Problems implementing micro services on immature organizations

  • Different teams create different micro services that do the same thing— “I need a new micro service and I’ll create my own”;
  • Micro services are not reused;
  • New micro services are not properly communicated between teams;
  • Teams don’t know how to deal with versions;
  • People don’t understand that legacy specific data must be cut;
  • People don’t adhere the mindset of isolating legacy;
  • Different teams don’t communicate with each other;
  • Politics overcomes what’s really important;
  • Projects have short time, teams are overloaded, unsatisfied and tired;
  • Quality is compromised;




Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Marcelo Cure

Marcelo Cure

More from Medium

Data Access between Micro/Services

SAGA Distributed Transaction Pattern in Microservices

Domain-Driven Design and Microservice Boundaries

Event Sourcing for an Inventory Availability Solution