syncing data across microservices, event-driven or rpc tho
Freja Eriksson
·2803 views
Hey everyone, I'm trying to figure out the best way to keep data consistent across a few main microservices. We've got user profiles and order history, and they really need to be in sync. My gut tells me an event-driven approach with a message queue (think Kafka or RabbitMQ) would be good, where services just put out events when something changes. That seems more separated, you know? But then again, for some really important actions, a direct RPC call could give us instant feedback and make handling complicated transaction logic a bit easier. What have you all found in similar situations? When was event-driven the obvious choice, and when did RPC just work better?
37 comments