Skip to content

Details

With Redis Cluster underway. The spec published (http://redis.io/topics/cluster-spec) and cluster code (https://github.com/antirez/redis/blob/unstable/src/cluster.c) in unstable branch. This event will be for SF Redis Devs on the cutting edge.

This meetup was created by the SF community due to a demand for cluster; but by the look of things 2.8 is a stepping stone to cluster (http://antirez.com/news/49?goback=%2Egde_3684309_member_214306417).

The meetup will be part discussion and part hack night. With SF Redis devs sharing experiences with current large clusters, demands for Redis cluster and an open floor for the SF commuity.

We're planning a round table format to share experiences, but also seeking speakers to share Redis cluster management experiences. If you're interested in talking, please email ben@redistogo.com

Refreshments will be provided, come early and be prepared to participate, this is more of a round table discussion than our previous events.

-----

Monday Update

Happy Afternoon Fellow Redisrs

I would like to thank everyone for signing up; we're almost at 70 registations.. which should mean a good crowd of Redis Devs.

This meetup will be ran in the BarCamp (http://en.wikipedia.org/wiki/BarCamp) format, We don't have a feature speaker instead its a chance to discuss current large Redis deployments, review of Redis Cluster Draft (http://redis.io/topics/cluster-spec), A review of the specifics of 2.8 cluster branch (https://github.com/antirez/redis/tree/2.8). We will kick off with an overview of everyones intrested and excitement for Redis Cluster, and will spend the next two hours how people think is best. Either as a group, in breakout sessions or as a mini hackacthon.

Unfortunately Salvator won't be attending this meetup but will be at another event on Thursday at 8:30pm (https://www.meetup.com/San-Francisco-Redis-Meetup/events/123141892/). He was sad to miss it, but said..

I'm very interested in feedbacks about the applicability of the system to real-world problems users will face in the real world.Redis Cluster is a subset of the usual commands available, and this subset has to deal with things like netsplits (the minority side becomes unavailable after the node_timeout time has elapsed). Moreover since data is distributed across many nodes it is not possible to write a key being sure the next write will work, and so forth.

Basically Redis is going to face the classical problems of distributed databases and my guess is that users need to adapt the programming style :-)

I'll be gathering a list of the communities uses for cluster, and will be sharing on the Redis Google Group.

We've a fresh keg at the Rackspace office and will have pizzas arriving at 6:30. Please bring your laptop, and if you would like to present anything on cluster please e-mail me at ben@redistogo.com

Related topics

You may also like