Developer at Noback's Office
Web application frameworks are indispensable. You wouldn't want to deal with raw HTTP messages yourself, nor build your own router, or ORM. But if you're not careful, a framework will take over your entire project. Business logic and framework-specific code will end up being mixed together, in controllers, services and entities. Not being able to describe the use cases of your application without also talking about HTTP, or SQL, leads to hard-to-test and hard-to-change application code. Your core code will be tied to your framework, which endangers the future of the project in the long term.
In this talk I'll explain how to make a clean separation between your own business logic and the code that makes your application's use cases available to the world outside. We'll discuss architectural concepts like "layers" and "ports & adapters", and how applying them will make your application flexible enough to deal with a constantly changing environment.
In this workshop we’ll dive into the topic of Autonomous Service development, with a sandbox project containing several interdependent services. These projects send messages to each other, and they call each other to retrieve data. In other words, they’re not autonomous at all. We’ll figure out some ways in which we can invert dependencies and leverage a messaging solution to achieve autonomy after all.
In a relatively short period you’ll get acquainted with the basics of asynchronous integration, CQRS, domain events, and integrating bounded contexts. There will be a healthy mixture between theory and practice. We look at different ways in which services can be dependent on each other: by directly sending queries or commands, or by knowing too much about each other's domain. We explore alternatives to improve the situation, increasing autonomy with every exercise. Because we'll be working with an actual application, it'll be clear that there is a trade-off involved in making a service truly autonomous. We discuss the costs, the benefits, and the reasons for splitting monolithic applications into services.
This is a training for developers who have experience working on a monolithic application and are now looking for ways to split the application into multiple applications that can work together, without depending too heavily on each other. The sandbox project we use for this training is built with PHP (without a particular framework) and requires Docker to run on your laptop. If you have experience with another object-oriented language, you should be able to do the exercises as well.
Matthias Noback is a professional web developer (since 2003). He lives in Zeist, The Netherlands, with his girlfriend, son, and daughter.
Matthias has his own web development, training and consultancy company called Noback's Office. He has a strong focus on backend development and architecture, always looking for better ways to design software.
Since 2011 he's been blogging about all sorts of programming-related topics on matthiasnoback.nl. He's published several programming books as well (most recently: "Principles of Package Design" and a "Style Guide for Object Design").See all speakers ›