We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
🚀 Common Mistakes When Moving to Microservices (Jakub Nabrdalik)
Avoid common pitfalls when transitioning to microservices by recognizing the importance of clear communication, team collaboration, and an architecture guild.
- Don’t assume that moving to microservices will automatically solve all problems.
- Poor communication between teams can lead to misunderstandings and errors.
- It’s essential to understand the constraints and requirements of each service.
- Microservices can lead to greater instability and failure rates if not implemented correctly.
- The architecture team’s role is to provide guidance and help teams make informed decisions.
- The development team should be responsible for designing their own architecture.
- The architecture guild’s goal is to create a shared understanding among teams.
- The guild provides a framework for teams to work together.
- The guild’s meetings should be focused and on-topic.
- The guild should produce a README file with guidelines for new teams.
- The guild can help teams overcome common mistakes, such as ignoring the constraints of the system.
- The guild can provide a shared understanding of what a microservice is and what its responsibilities are.
- The guild’s meetings should be open to all employees, not just the tech team.
- The guild’s documents should be public and accessible to all teams.
- The guild’s goal is to increase transparency and understanding among teams.
- The guild’s meetings should be focused on decision-making and problem-solving.
- The guild’s members should be chosen for their expertise and willingness to collaborate.
- The guild’s goal is to create a standardized way of working.
- The guild’s meetings should be recorded and made publicly available.
- The guild’s guidelines should be followed by all teams.