On Tue, Apr 6, 2010 at 7:08 PM, Manik Surtani <[email protected]> wrote:
>
> On 6 Apr 2010, at 12:37, Philippe Van Dyck wrote:
>
>> Hi guys,
>>
>> just a short update about the status of the Infinispan (S3) Store:
>> -Code is ugly, not production ready, but running flawlessly
>
> Is this the CloudCacheStore you're referring to? There are a couple of bits
> where it can be improved, yes. There are some open JIRAs on this.
No Manik, mine ;-) My qi4j store code.
>
>> -Infinispan memory cache eviction mechanism is based on a memory
>> threshold (i.e. you specify 100MB of memory for the cache in the store
>> config)
>
> No, it is based on number of entries. E.g., you specify 1000 entries as a
> high water mark. Or have you implemented a layer on top of this?
Yes, since I only store bytes buffers, it is quite easy to implement
but it should definitely be implemented one layer up (in infinispan)
>
>> -RHQ monitoring with Infinispan plugin works (beautifully)
>
> :)
>
>> -Entries are gzipped on S3 (patch now included in infinispan-alpha1)
>> -Wicket load balancing is done with infinispan (custom pagestore)
>> -I use a directory structure for qi4j identities ("Entity1/key1") and
>> there is a webdav interface to it (I can mount qi4j's store in Finder)
>> -EC2 S3_PING is used in jgroups to join the cluster of qi4j stores
>> -Each qi4j uow is transaction backed with rollback support (I
>> currently use Atomikos as TM - not fully tested)
>> -S3 (blobstore) acces is using Infinispan synchronous and transacted mode
>> -EC2 images only contain the wicket web interface with a jetty https
>> connector / when added to amazon elastic load balancer, infinispan
>> connects to the cache cluster and wicket begins to server load
>> balanced requests - yep, just like that
>>
>> Current performance, as reported by RHQ, from EC2 to S3, is around
>> 60ms per read/write from S3 (rough average).
>> I have not yet done elastic load balancing load tests with loadStorm.
>>
>> I don't know any NOSQL alternative offering a permanent transacted
>> monitored compressed Finder-mounted clustered load-balanced store ;-)
>
> :-) Nice stuff. I think we have a way to go still though, specifically in
> the areas of eventing (especially when using HotRod), txs over HotRod, truly
> scalable indexing and querying, natural language querying (SQL, JPA-QL, etc)
> and Mircea's personal favourite, continuous queries. Once we have these in
> place, I think we'd not only lead the NoSQL space, but also make headway into
> CEP.
Indexing and querying is managed by qi4j... maybe you should take a
look at it, the whole idea behind qi4j, COP (yeah, I have acronyms
too), is amazing... (http://www.qi4j.org/)
phil
>
> --
> Manik Surtani
> [email protected]
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
>
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
