What you’ll learn The problem BFF solves If multiple clients (web, mobile, partner apps) call the same “generic” backend, you often end up with: Backend for Frontend (BFF) fixes this by creating a backend tailored to a specific frontend: BFF in one sentence A BFF is a client-specific backend that aggregates and shapes data exactly… Read More »
What you’ll learn The problem: distributed transactions without a 2PC In a monolith, you might wrap changes in a single database transaction. In microservices (or distributed systems), a single business action often spans multiple components: You can’t easily use a single ACID transaction across multiple independent datastores and services (and you generally shouldn’t). Saga is… Read More »
What you’ll learn Video discussion on YouTube – https://youtu.be/2lFW5H3ZzLA The problem CQRS solves In many systems, we try to make one database schema do everything: As the system grows, that single model starts to hurt: CQRS (Command Query Responsibility Segregation) is a pattern that says: CQRS in one sentence CQRS separates the write path (commands)… Read More »