Sam Newman @ Sam Newman & Associates
June 14th, 2021, 15:05–16:30 CEST
Much of the attention for microservice architectures tends to focus on the technical aspects. But when you look into the details of organisations that have benefited from this approach you realise that there is more to getting the most out of microservices than lots of shinny new technology.
In this talk, Sam will show how organisational structures and team responsibilities may need to change if you want to get the most out of adopting a microservice architecture. Looking at traditional IT structures and comparing them with the modern autonomous delivery teams, he’ll explore how to get the organisation and architecture working well together. From Conway’s law to Dunbar’s number, stream-aligned to two pizza teams, you’ll see how you can start to apply these ideas inside your own company.
Joseph Yoder & Paulo Merson @ respectively, The Refactory & Brazilian Federal Court of Accounts (TCU)
June 14th, 2021, 19:00–19:45 CEST
Many Microservices architectures start from the evolution of a Monolith system by gradually applying the microservices architectural style. There are considerations and principles that assist with successfully evolving from a monolith to Microservices. Deciding what to decouple along with when and how to incrementally evolve a system are the main architectural challenges in this process. There are good principles that help with this evolutionary process. For example, it is important to commit to “stop adding to the monolith” - all new code is added as microservices. The new features are microservices, occasionally replacing part of the monolith. Also, there might be important pieces of the monolith that are getting hard to maintain and you want to pull these out. When this happens, you find design seams within the monolith, which can be refactored out to components that can ultimately be replaced with microservices. This is the core of the “Strangler Pattern”. Beyond the strangling of a monolith, there are other considerations for organizations that make the strategic move to microservices, such as operational readiness and technical skills. Early on, it is ok to create macro services first and then evolve (refactor) them to microservices. Also, when writing new microservices code, it is important to avoid dependencies to the monolith. This talk will examine various scenarios when evolving from the monolith to microservices specifically with variations of the Strangler Pattern.