Mi­croser­vice Pit­falls

How mi­croser­vices can cor­rupt your data - even with even­tu­al con­sis­ten­cy or sagas

What every ar­chi­tect should know be­fore se­lect­ing the next big bro­ker / in­te­gra­tion plat­form, cloud DBMS or re­mot­ing stack. Or: how mi­croser­vices can cor­rupt your data - even with even­tu­al con­sis­ten­cy or sagas.

Are you start­ing your next mi­croser­vices project and won­der­ing what tech­nolo­gies to se­lect? Let's face it, there are too many prod­ucts to choose from. Just be­cause some­thing is new and hip doesn't mean it will serve you best. While we all like to dec­o­rate our re­sume, no­body likes be­ing part of a fail­ing project.

Our ad­vice

Don't start with the tech­nolo­gies - rather: mind the pit­falls and elim­i­nate the range of op­tions ac­cord­ing­ly. Sub­scribe to our email course and get the pit­falls de­liv­ered straight to your in­box (one mes­sage per week for a few weeks).

Ready for the chal­lenge? Here is what you will learn:

• How mes­sages can be lost - even with the per­fect in­te­gra­tion plat­form (in­clud­ing the lat­est great­est like Kaf­ka or Rab­bitMQ)
• Du­pli­cate mes­sages and how to avoid them - so you don't need the com­plex­i­ty of idem­po­ten­cy
• How re­mot­ing can cor­rupt your data - bet­ter think of this be­fore you im­ple­ment that REST ser­vice
• Poly­glot per­sis­tence & NoSQL pit­falls - the dev­il is in the back­ups
• How to make your Kaf­ka, Rab­bitMQ or NoSQL more re­li­able