INTERMEDIATE · 8 MODULES · 64 LESSONS

System Design Fundamentals

Take a vague prompt like designing a URL shortener and turn it into a scalable design you can defend with numbers, diagrams, and clear tradeoffs.

For you if
You write backend code and want systems that handle scale, or you're prepping for system design interviews.
By the end
You'll know how to estimate capacity, add caching, scale the database, balance load, and weigh consistency against availability.
You need
Basic Python and a working grasp of relational databases and HTTP APIs. No distributed systems experience needed.
  1. 01Cómo abordar un problema de system design8 LESSONS
    1. Module introduction: understand the problem before you draw
    2. Functional vs. non-functional requirements
    3. Asking the right clarifying questions
    4. Scoping: cut the problem down to size
    5. The 4-step framework
    6. Enlace in a single box
    7. Thinking in tradeoffs and where the box breaks
    8. Mini-project: from a vague prompt to requirements and scope
  2. 02Estimación de servilleta (back-of-the-envelope)8 LESSONS
    1. Module introduction: the napkin before the server
    2. The tools: powers of 10, seconds per day, and units
    3. QPS: from requests per month to requests per second
    4. Storage: how much disk in five years
    5. Bandwidth: how many bytes per second come in and out
    6. Memory: the working set and why it fits in RAM
    7. Smart rounding and sanity checks
    8. Project: Enlace's capacity table
  3. 03Modelo de datos y generación del código corto8 LESSONS
    1. Module introduction: from the number to the model
    2. The `Link` record
    3. SQL vs NoSQL for Enlace
    4. Generating the code with a hash: collisions measured
    5. Global counter + base62 (and random + verification)
    6. `base62_encode`/`base62_decode`, run
    7. Choosing the strategy
    8. Project: Enlace's `short_code` generator
  4. 04Caché — el camino de lectura pesada8 LESSONS
    1. Module introduction: the read rules
    2. Why Enlace desperately needs a cache
    3. The cache-aside pattern
    4. Eviction policies and LRU
    5. Hit ratio and average latency
    6. The working set and the 80/20 rule
    7. TTL and cache invalidation
    8. Project: size Enlace's cache
  5. 05Escalar la base de datos8 LESSONS
    1. Module introduction: when the single box no longer holds up
    2. When one database is not enough
    3. Replication: primary and replica
    4. Replication lag and reading from replicas
    5. Sharding and the shard key
    6. The `hash(key) % N` problem
    7. Consistent hashing, executed
    8. Project: a sharding and replica plan for Enlace
  6. 06Balanceo de carga y statelessness8 LESSONS
    1. Module introduction: the last bottleneck
    2. What is a load balancer
    3. Load balancing algorithms
    4. Stateless versus stateful services
    5. Where the session lives
    6. Health checks
    7. Scaling horizontally by adding instances
    8. Project: design Enlace's load balancing layer
  7. 07Fiabilidad y el tradeoff de consistencia8 LESSONS
    1. Module introduction: when the machine goes down and the network splits
    2. Redundancy and single points of failure
    3. Failover basics
    4. The CAP theorem, explained (without the myth)
    5. PACELC: beyond CAP
    6. Strong versus eventual consistency, and Enlace's choice
    7. SLA, SLO and the nines, executed
    8. Project: choose and justify Enlace's consistency model and its SLO
  8. 08Proyecto — diseña Enlace de punta a punta8 LESSONS
    1. Module introduction: the journey back
    2. Step 1: Requirements and scope for Enlace
    3. Step 2: The capacity table, executed
    4. Step 3: High-level design and the diagram
    5. Step 4a: The write path
    6. Step 4b: The read path and the cache
    7. Step 4c: Scaling out with replicas, sharding, load balancing and consistency
    8. Project: design Enlace end to end
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