INTERMEDIATE · 8 MODULES · 64 LESSONS

Architecture Decisions and Trade-offs

Make architecture decisions with evidence instead of personal preference: compare options with numbers, record the why, and protect each decision with an automated test.

For you if
You design or maintain backend systems and struggle to defend why you picked one option over another.
By the end
You'll know how to build a decision matrix, write an ADR, test alternatives before committing, and weigh how costly a decision is to reverse.
You need
Experience with backend systems (services, APIs, databases) and Python to run the exercises.
  1. 01La arquitectura es decisiones8 LESSONS
    1. Module introduction: architecture is decisions, not diagrams
    2. What makes a decision architectural
    3. Local versus architectural decisions
    4. The cost of deciding
    5. The cost of NOT deciding
    6. Deciding under uncertainty
    7. Architecture is decisions, not diagrams
    8. Mini-project: classify and prioritize Mercado's open decisions
  2. 02No hay "mejor", solo trade-offs8 LESSONS
    1. Module introduction: there is no "best", only trade-offs
    2. What "good" means: the quality attributes
    3. Why quality attributes compete
    4. The trade-off is your deliverable
    5. Quantify, don't adjectivize
    6. Performance costs freshness: the cache trade-off
    7. There is no context-free "best"
    8. Project: quantify and name a Mercado trade-off
  3. 03Los Architecture Decision Records (ADR)8 LESSONS
    1. Module introduction: the ADR, the team's memory
    2. Why an ADR is written: architectural amnesia
    3. The anatomy of an ADR: Context, Decision, Consequences, Status
    4. The status of an ADR: proposed, accepted, superseded, deprecated
    5. The decision log: the numbered and immutable memory
    6. Supersede: replacing a decision without erasing the history
    7. Lightweight ADRs versus heavy documentation
    8. Project: write and validate Mercado's decision log
  4. 04La matriz de decisión8 LESSONS
    1. Module introduction: the decision matrix
    2. The anatomy of a decision matrix
    3. Choosing the criteria that matter
    4. Scoring options on a common scale
    5. Weights without rigging the result
    6. Sensitivity analysis and false precision
    7. The matrix is a thinking aid, not an oracle
    8. Project: score a Mercado decision with a matrix
  5. 05Generar y probar opciones8 LESSONS
    1. Module introduction: generating and testing options
    2. Generate at least three options
    3. The first-idea bias and anchoring
    4. The spike: buying information with an experiment
    5. Timebox the spike and throw it away
    6. The walking skeleton
    7. Decide with evidence, not the loudest voice
    8. Project: run a spike for a Mercado decision
  6. 06Fitness functions y arquitectura evolutiva8 LESSONS
    1. Module introduction: fitness functions and evolutionary architecture
    2. What is a fitness function
    3. The forbidden dependency
    4. Measuring coupling as a fitness function
    5. Atomic and holistic fitness functions
    6. Fitness functions in CI: the gate
    7. Evolutionary architecture: changing safely
    8. Project: protect a Mercado decision with a fitness function
  7. 07El costo y la reversibilidad de las decisiones8 LESSONS
    1. Module introduction: the cost and reversibility of decisions
    2. One-way and two-way doors
    3. Calibrate the rigor to the reversibility
    4. The last responsible moment
    5. Technical debt as a deliberate trade-off
    6. The technical-debt quadrant
    7. Make one-way doors reversible
    8. Mini-project: cost and reversibility of a Mercado decision
  8. 08Proyecto — decide y registra una decisión de Mercado8 LESSONS
    1. Module introduction: the return journey
    2. Is this an architectural decision? Calibrate the rigor
    3. Generate options and run a spike
    4. Quantify the trade-off
    5. Score the matrix and stress-test it
    6. Write the ADR
    7. Protect the decision with a fitness function
    8. Project: decide and record a Mercado decision
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