On Tue, Jan 25, 2011 at 6:25 PM, Rickard Öberg <[email protected]> wrote:
> Yeah, the longterm goal is to have local EventSource capture, then Atom feed > producer+consumer, and then replay. With that you can build any type of > replication infrastructure you want (master/slave, multimaster, staging > servers with production data, backups, etc.). I think you made that sound a LOT easier than it in reality is, if you are going to allow for arbitrary failures of any underlying component. A lot of scalability infra is not around 'replication of data', but fan out to enough compute (or even memory) power. For typical web requests you are fine, since the client waits and it can all be within a transaction of that request, but once you introduce fire-forget semantics, things quickly get very tricky... That is my day job right now :-) Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
