thanks for the links. i hadn't read the paper. it seems like the design patterns book in that it's a good reference to, um, refer back to when looking at the

thanks for the links. i hadn't read the paper. it seems like the design patterns book in that it's a good reference to, um, refer back to when looking at the latest "new" thing. going back to the parent comment, > I would love to learn more and avoid mistakes made during it's infancy. you'll probably want to look at zookeeper (or some system built on top of zookeeper like storm) if you expect the thing to grow into a large project with lots of services. and to the article, > Should all your applications use the same language? there are definitely reasons (library availability, runtime capabilities, the simple fact that you don't have to, and so on) not to use the same language, but i've found being able to refactor between applications very helpful.