Microservice Pitfalls
How microservices can corrupt your data - even with eventual consistency or sagas

trap-33819 640.png

What every architect should know before selecting the next big broker / integration platform, cloud DBMS or remoting stack. Or: how microservices can corrupt your data - even with eventual consistency or sagas.

Are you starting your next microservices project and wondering what technologies to select? Let's face it, there are too many products to choose from. Just because something is new and hip doesn't mean it will serve you best. While we all like to decorate our resume, nobody likes being part of a failing project.

Our advice

Don't start with the technologies - rather: mind the pitfalls and eliminate the range of options accordingly. Subscribe to our email course and get the pitfalls delivered straight to your inbox (one message per week for a few weeks).

Ready for the challenge? Here is what you will learn:

  • How messages can be lost - even with the perfect integration platform (including the latest greatest like Kafka or RabbitMQ)
  • Duplicate messages and how to avoid them - so you don't need the complexity of idempotency
  • How remoting can corrupt your data - better think of this before you implement that REST service
  • Polyglot persistence & NoSQL pitfalls - the devil is in the backups
  • How to make your Kafka, RabbitMQ or NoSQL more reliable