A way to isolate business logic in code — Table of contents History Purpose Principles The separation of concerns Three Layers Inner layer isolation — dealing with dependencies Ports and Adapters Domain in isolation Direction of flow Ease of testing Sample with Spring and Kotlin Hexagonal vs Onion vs Clean Conclusion Reference A bit of history Published in a blog by Alistair Cockburn in 2005 The…

The building blocks of DDD tactical design — The domain-driven design is a technique to model and build a software with business domain centricity. In other words, it enables us to map the real-world problem-space to a modelled solution space. The DDD approach comes with a toolbox that is split in 2 parts : Strategic Design Tactical Design …

The tactical design phase to translate the business needs into code — DDD is an approach to tackle the complexity of a system, and align the understanding of the business domain between domain and technical experts. As described in my previous articles, it comes with a set of tools : Domain-Driven Design (DDD) — The Strategic Design Domain-Driven Design (DDD) — The…

All you need to know about software architectures — their purpose, core principles, and rules, their role in an organisation and their impact on dev teams. — Developing software requires much effort and taking into account multiple aspects. However, the critical mission should be customer-centricity. It implies the software is there to serve our end users and fulfil our customers' needs. As a matter of fact, users are more nowadays demanding than 20 years again when consuming…

How we have put the place the continuous Quality Gate — Following “The need of a Quality Gate at TheFork”, we are going to walk through the way to setup the Quality Gate (QG) on the Continuous Integration (CI). As we were already using Sonarcloud, we just needed to create a QG with specific conditions depending the nature of the project…

Sorting out the technical debt and enforce the quality by first tackling the new code coverage — I joined the TheFork about 9 months ago. Yet I’ve learned many things. I’m more than happy to share my experience throughout this article. …

Evolving from monolith toward a distributed system — In the first years of my career, Service-Oriented Architecture (SOA) rang my bells, as many seniors and architects were talking very much about it. And the buzz was quite strong, but not as strong as microservices which is also promoted by the DevOps movement. At that time, I understood very…

The benefits and drawbacks of a modular architecture — This architecture has been hyped for about a decade now. The intent was to divide a complex system (back then monolith) into sub-systems that take up single responsibility as a service. They have their own characteristics and come with benefits and drawbacks. …

a rapid technique to explore the the business domains and tackle its complexity — Domain-driven design, a.k.a DDD, is an approach to build complex systems with the business domain centricity, and comes with a toolbox composed of a few concepts and building blocks, as described in my previous articles : Domain-driven design (DDD) — The Strategic Design Domain-driven design (DDD) — The Tactical Design