The ruby implementation I'm working on was intended for the below -
local testing of clients and publishers, a quick hub out of the box with
a local tool chain -- a simple ruby port that passes the test suite.
I could probably move redis to mysql/postgresql pretty quickly if people
are interested. It would give better visibility into the data -
although, long-term scaling I was still thinking maybe sqs and s3.
Thanks,
Mike
Brett Slatkin wrote:
On Tue, Jan 19, 2010 at 9:59 PM, Tim Bray <[email protected]> wrote:
On Tue, Jan 19, 2010 at 9:20 PM, todd hoff <[email protected]> wrote:
Thanks Julien. So no other hubs are available yet? That seems strange.
Well, building one that scales is going to be a lot of work and
require considerable infrastructure, and the business model isn't
self-evident. To me at least. Having said that, I'd love to, it'd be
big fun.
Scaling is important for shared services, but I think having a hub
implementation that works out of the box for people (e.g., on the lamp
stack) and scales to at least ~10 updates per second would be good
enough for most users to deploy for themselves.
