Connell

This is a story about how our team at Stack Overflow split out a small feature from a monolithic application into its own microservice. We moved the data to a new database, rebuilt the UI as a microfrontend using a new framework, and managed to deploy it without any downtime.

Deciding which things belong in which part of your system can make or break your architecture. To avoid creating a big ball of mud, we separate concerns and keep things organised. This talk takes us through different kinds of boundaries: What makes a good function? What makes a good class? A good service? We’ll discuss slicing vertically, building separate packages, and the trade-offs of splitting into many git repositories.

A 20 minute talk outlining the purpose of the new cross-functional platform team at our company, our vision for the future, and how we intend to get there.

Explaining how I reason about the building blocks of Onion Architecture, Domain-Driven Design and Command Query Responsibility Segregation in an event-driven microservices architecture. How it all fits together in my head, the concepts they share, and the mistakes I've made along the way.