Definitely a good read for (Josh and Tom)

[Simo Sentissi]

I never used the amazon services karma uses (SQS and SNS) to wire thing up, but I believe that is a really good read:

https://blog.yourkarma.com/building-microservices-at-karma

On our side we are all http on the request-response services, however with iron.io releasing their solution for on premise I strongly believe that a setup could have the front end apps hit the http backend end-points directly and if not available then queue them up on the nifty iron.io http rest queues.

Cheers!
-Simo

[Josh Adams]

This was a great read.  Really enjoyed it.  It's also funny to me how a lot of this complexity goes away with various erlangy patterns (but that only works up to 13 or so nodes - beyond that you need to break systems up and have a more 'normal' intra-system comms mechanism)

(Accidentally sent this only to simo the first time, so sorry for the double post simo)

[Josh Adams]

Along moderately similar lines: http://www.tigerteam.dk/2014/microservices-its-not-only-the-size-that-matters-its-also-how-you-use-them-part-4/

This is the best article so far among all these 72 microservices-related articles: http://blog.arkency.com/2014/07/microservices-72-resources/