Om sesjonen
Service layers often start simple but slowly turn into a mix of business logic, infrastructure calls, and "just one more thing". The result is hard-to-read code, fragile tests, and a structure that depends more on discipline than design.
There are well-known solutions like onion, hexagonal, or clean architecture. They work - but they also require a lot of upfront understanding and ongoing effort to keep intact. In practice, many teams don't fully adopt them.
In this talk, I'll share a small, practical approach I've used to bring structure back into service layers - without introducing heavy patterns or requiring everyone to "buy in" to a big architectural model.
We'll look at a real example, how it evolves, and what changes make the biggest difference. The focus is on something you can apply immediately, even in an existing codebase.