BEGINNER · 8 MODULES · 64 LESSONS

Architectural Styles and Boundaries

Decide how to split a system from the inside: where to draw boundaries, when a modular monolith is enough, and when microservices really pay off.

For you if
You work in a monolith where everything touches everything and each change breaks something far away.
By the end
You'll know how to draw bounded contexts, extract services gradually, and defend a boundary with coupling metrics.
You need
Basic Python and experience on a backend with several modules. No microservices experience needed.
  1. 01Acoplamiento, cohesión, y por qué la estructura importa8 LESSONS
    1. Module introduction: the Mercado monolith where everything touches everything
    2. What coupling is
    3. The types of coupling
    4. Cohesion: the other force
    5. The cost of change, measured
    6. High cohesion, low coupling
    7. The code smells of bad coupling
    8. Mini-project: measure Mercado's coupling
  2. 02Límites y bounded contexts8 LESSONS
    1. Module introduction: from the forces to the boundary
    2. What a bounded context is
    3. The five bounded contexts of Mercado
    4. Ubiquitous language per context
    5. The same concept means different things
    6. The boundary as a contract
    7. Signals for where the boundary goes
    8. Mini-project: map the bounded contexts of Mercado
  3. 03El monolito modular8 LESSONS
    1. Module introduction: Mercado without microservices
    2. What a modular monolith is
    3. A module with a public interface
    4. Forbidding imports of internals
    5. From ball of mud to modular in Mercado
    6. Transactions and simplicity in one process
    7. When modular is enough (and you don't need microservices)
    8. Project: modularize a Mercado module
  4. 04Microservicios — qué ganas y qué pagas8 LESSONS
    1. Module introduction: the bill almost nobody reads
    2. What a microservice is (and is NOT)
    3. What you gain: four independences
    4. The cost of the network, executed
    5. Distributed consistency without ACID
    6. Observability and distributed debugging
    7. When YES and when NO
    8. Project: extract a context and justify the cost
  5. 05Comunicación a través de los límites8 LESSONS
    1. Module introduction: how the two sides of a boundary talk
    2. Synchronous vs asynchronous communication
    3. Temporal coupling: the price of waiting
    4. The event as decoupler
    5. Orchestration vs choreography
    6. The boundary as a versionable contract
    7. Choosing synchronous or asynchronous at each Mercado boundary
    8. Project: define the communication style of each Mercado boundary
  6. 06Estrategias de descomposición8 LESSONS
    1. Module introduction: how to cut without bleeding
    2. Decompose by business capability, not technical layer
    3. The strangler fig pattern
    4. The distributed monolith trap
    5. A database per service
    6. Shared data and re-coupling
    7. What to extract first in Mercado
    8. Project: Mercado's decomposition plan
  7. 07Medir y defender los límites8 LESSONS
    1. Module introduction: measuring and defending boundaries
    2. Why measure boundaries
    3. Fan-in, fan-out and the coupling metrics
    4. Instability and the Stable Dependencies Principle
    5. Detecting cycles between modules
    6. Fitness functions and architecture tests
    7. Conway's Law and the team↔boundary map
    8. Project: measure and defend Mercado's boundaries
  8. 08Proyecto — Reestructura Mercado8 LESSONS
    1. Module introduction: the trip back down
    2. Step 1: draw Mercado's context map
    3. Step 2: choose the style (modular monolith first)
    4. Step 3: what to extract first, with the strangler fig
    5. Step 4: define the communication of each boundary
    6. Step 5: measure the coupling, before and after
    7. The decision record: gather the five pieces
    8. Project: restructure Mercado (final deliverable)
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab