Hacker News Reader

With a good old fashioned message broker for guaranteed eventual delivery, decoupling, discovery and elasticity (if you can fit it in to your setup)

View on HN

I can't tell if this is a joke or not.

I'm not joking. Just to be clear, I'm taking asynchronous to mean a call that is not transactional. Where you are ok with eventual consistency. If something is transactional then keep it in one service. Make it an action not a transaction and save yourself a lot of grief.

So if something is asynchronous then why not back it up with a message broker and get the properties I listed (in earnest).

I'd be interested to know if anyone's had success with distributed transactions in a microservice architecture. I've gotten into a world of pain every time I've tried.

We did have some success at one of my previous companies (wiggle.co.uk), but that was mainly due to pretty tight integration between MSMQ, MSDTC and MS Sql Server. Even then, we tried to avoid distributed transactions as much as possible.

Reply on news.ycombinator.com