We have an abstraction library at work we plan to release in coming weeks (although we've been saying that for a year now) called "drumbeat". We have libraries

We have an abstraction library at work we plan to release in coming weeks (although we've been saying that for a year now) called "drumbeat". We have libraries in Ruby, Go and Java, and the concept is that developers should not have to worry about transports or how they work: you make it as simple as possible for most developers in the org to work with distributed systems, and they'll start working with distributed systems, and the arcane understanding of exactly what the trade-offs are between different vendors and messaging technologies can be centralised to a few devs with ops support instead of it being bikeshedded to death. This is nice in that it becomes scalable and transparent with little refactoring in Go, but having multi-language support is useful, otherwise we'd probably drop drumbeat and use this instead. It does suggest we should think about how best to do this in Go again though - I like the pattern a lot.