Рет қаралды 68
Besides the question: “How big should a microservice be?”, there is, in my opinion, a much more important question to clarify first: “What does the service deal with?”. Often this question is answered “wrong” and the consequences can be fatal, because too often an entity is used to define the microservice. This leads to a shared kernel, a distributed monolith and a dependency hell.
This talk will help to identify this anti pattern and offer ideas to avoid or change it.
✨Speaker - Lukasz Goworko ✨
Lukasz works as Engineering Manager at NewStore. He is a clean code and DDD enthusiast and a constant advocate of agile methods. As part of the IT team he helps to plan and implement the successful development of an evolvable and maintainable platform by applying appropriate methods and tools.
You can join NewStore meetups at www.meetup.com...