On 26th of September 2019 I had an opportunity to attend Team Topologies Fundamentals training in Leeds - the session was delivered by Matthew Skelton. Together with Manuel Pais he wrote a book called Team Topologies that discusses how to "build the best team organization for your specific goals, culture, and needs".
The training was organised into 4 sections:
Both the book and content of the training are based on 5 years of research across 30+ organisation in multiple industries and various countries / cultures. The authors focused on distilling underlying principles, patterns and topologies. This allowed them to focus on the essence of team design, rather than on more specific challenges related to a particular industry. Read More
When designing the architecture of a distributed / microservice system, one of the patterns used often is to make components communicate over an asynchronous message queue / bus / streaming platform. This approach has a lot of benefits, such as reduced coupling, improved resiliency and fault tolerance. It also creates some challenges, and one of them is finding an answer to a question: "Who defines and owns the protocol that services use to exchange messages?". Read More
Running a projection doesn't have to mean that all we can do is to update read models used by APIs. It is possible to handle more complex use cases that involve triggering side effects on other systems, and still keep the code concise and resilient. Read More
Event Sourced systems implemented in tandem with Command Query Responsibility Segregation can handle very high volume of events and still deliver great experience for the users.
Because the Write Stack (command handling) is clearly separated from the Read Stack (query handling) we can prioritise which read models get updated first and which can be updated a bit later in case of a spike in traffic. Read More