Remember when building the frontend was fun? From simple web pages to mind-bending meta-frameworks, the modern frontend has become an accidental monster. This is the story of how it happened and how we might tame it.

We adopt patterns like Clean and Hexagonal Architecture to fight complexity, but often end up creating more of it. This post dives into why this happens and how a pragmatic approach focused on value and evolution can save your codebase from the "best practice" trap.

Inversion of control is one of the most important concepts in object-oriented programming that forms the base of popular architectures like the onion, hexagonal and clean architectures. In this article, I’ll answer the following questions: * What's Inversion of Control? * How is it implemented in the Spring framework?

Deciding whether something should be an entity or a value object can be tricky even for developers experienced in domain-driven design. In this issue, I'll clarify the differences so we understand these concepts once and for all! Let's get started! Entities and Value Objects as Classes

In this article, we will answer the following questions: What is eventual consistency? Is it better than strong consistency? And do we have any other option? Let’s discover it in the next few minutes! Strong Consistency Defined Strong consistency guarantees that read operations receive always the most recent data.

In this article, I want to show you how I apply domain driven design (DDD), as well as clean, onion and hexagonal architectures concepts when I design and code a simple application. Rather than giving you a set of rules or definitions, I will explain what my thinking process is.

Authorization is difficult to implement and test because it’s multi-dimensional and requires a deeper understanding of our APIs. In this article, I’ll explain how authorization is broken and what we can do to protect our systems.

Despite many developers and teams feel confident about the security of their APIs, Broken Authentication is still one of the top API security risks according to the Open Worldwide Application Security Project (OWASP). In this article, we will understand why this issue is still so common and how we can

The State Design Pattern is a behavioral design pattern that allows an object to change its behavior when its internal state changes. It was introduced in the famous “Gang of Four” book titled “Design Patterns: Elements of Reusable Object-Oriented Software“. By the end of this article, you will have a

In this article, we explore the Hexagonal Architecture, as outlined by Alistair Cockburn in 2005, commonly referred to as the ports and adapters pattern. I will explain from a theoretical standpoint but also offer a concrete example that I’ve shared on GitHub. At the end, we will compare the

This article is a transcription of my video on the Clean Architecture by Robert C. Martin. It is part of a series of videos where we analyze some of the most popular architecture styles such as the Onion Architecture and the Hexagonal Architecture. Let’s get started! Clean Architecture Motivation

Whether you are a junior or senior developer, it can be difficult to understand what the hexagonal, clean, or onion architectures are. But, most importantly, it’s difficult to figure out how to use them when coding a real application. In this video, we will start by demystifying the concepts

Are you building software that’s meant to last? If so, you need to understand the importance of DDD aggregates in your domain model. Aggregates are essential to build reliable, maintainable, and scalable software that stands the test of time. But why do so many developers overlook this crucial concept?

Event Sourcing and CQRS are possibly the most fascinating architectural patterns in the software world, especially when combined with an event-driven architecture (EDA). In this article, we explain both patterns highlighting advantages and disadvantages of these approaches. In the conclusion, I will give you my personal opinion on whether these

In this article, I cover the “Backend for Frontend” pattern mentioned by Sam Newman in his “Building Microservices” book. You can also find the same content in video format on my YouTube channel. Introduction There are times when the typical general-purpose API backed by a microservice is not enough to

Stop making microservices the goal of your architecture. There’s nothing more complex to build and operate than a distributed system. That’s why we really need to have good reasons to adopt a “microservices architecture”. If you search the web for advantages of microservices, you’ll find this list.

In this article, we explain the concept of anemic model which is extremely common in modern applications. We also try to identify why anemic models are so popular, as well as proposing solutions to mitigate this issue. What is an Anemic Model? A model is anemic when its objects have

Domain Driven Design (DDD) is one of the pillars of object oriented software development. You must understand it really well if you want to produce future proof code and designs. Despite it looks intimidating to most developers, the concepts of DDD are really straight-forward and to some extent based on