Skip to content
learn
  1. Learn
  2. High Level System Design
  3. Architecture Styles

HLD-M14

Architecture Styles

How to shape a system: monoliths and modular monoliths, microservices, discovery and service meshes, serverless, domain-driven boundaries and incremental migration.

7 lessonsabout 70 min

Every system has an architecture, chosen on purpose or not. One deployable or many? Functions that run on demand, or servers that are always on? Where do the boundaries between parts go, and who owns each part? These choices shape how fast teams can ship, how the system fails, and how much infrastructure you have to run, often more than any single technology does.

This module compares the main architecture styles honestly. You will see why a well-structured monolith is often the right start, what microservices really buy (and cost), how services find each other and how a service mesh moves networking out of application code, where serverless shines and where it gets expensive, how domain-driven design draws boundaries that last, and how to migrate an existing system gradually with the strangler fig pattern instead of a risky rewrite.

Lessons

  1. HLD-14.01 Monolith and modular monolith A monolith is one deployable application containing all features. Beginner 10 min
  2. HLD-14.02 Microservices Microservices split a system into small services, each owning its data and deployed independently by its own team. Intermediate 14 min
  3. HLD-14.03 Service discovery In a dynamic environment, service instances come and go, so callers cannot hardcode addresses. Intermediate 8 min
  4. HLD-14.04 Service mesh A service mesh moves networking concerns out of application code into sidecar proxies deployed next to every service. Advanced 10 min
  5. HLD-14.05 Serverless and event-driven compute Serverless platforms run functions in response to events and bill only for execution time, scaling automatically from zero to thousands of instances. Intermediate 10 min
  6. HLD-14.06 Domain-driven design for architects Domain-driven design divides a business into bounded contexts, each with its own model and vocabulary, such as Billing or Shipping. Advanced 12 min
  7. HLD-14.07 Migrating architectures: the strangler fig The strangler fig pattern replaces a legacy system gradually instead of in a risky big-bang rewrite. Advanced 8 min

Start with lesson 1