Typorithm · medium

Deployment & Boundaries

microservices-deployarchitecturedeploymentstrangler-figconway

Saved on this device

Full lesson · 8 learning steps Open any exercise for focused practice

Step 1 of 8 · intro card

Learn Deployment & Boundaries

Distributed Data & Ops

Each service ships as its own container, scales independently, and has its own CI/CD pipeline. Conway's law means team ownership mirrors service boundaries, and you migrate off a monolith incrementally with the strangler-fig pattern rather than a big-bang rewrite.

A microservice is an independently deployable unit. It ships as its own container image, scales on its own, and runs through its own CI/CD pipeline — so a team can release its service without waiting on a single coordinated deploy of everything.

Conway's law observes that a system's structure tends to mirror the communicating teams that build it. Aligning one team per service turns that force into an advantage: clear ownership keeps service boundaries sharp and decisions local.

You rarely move to microservices in one leap. The strangler-fig pattern grows the new system around the old one, redirecting one capability at a time from the monolith to a new service until the monolith is gone — far safer than a big-bang rewrite.

Each service is its own container with its own CI/CD pipeline.

Conway's law: team ownership mirrors service boundaries.

Strangler-fig migrates off a monolith incrementally.

deployment:
  unit: container-per-service
  scale: independently
  ci_cd: pipeline-per-service
  org: team-owns-service
  strategy: strangler-fig-migration

Read the implementation

Connect each part of the code to the concept before you type.

1. Container per service

Each service ships as its own container image, deployed and versioned independently of the others.

unit: container-per-service

2. Independent scaling

Because services are separate units, you can scale a hot service up without scaling everything.

scale: independently

3. Pipeline per service

Each service has its own CI/CD pipeline so teams release on their own cadence without coordinating one giant deploy.

ci_cd: pipeline-per-service

4. Team ownership (Conway)

Conway's law: a system's structure mirrors the org's communication, so aligning one team per service keeps boundaries clean.

org: team-owns-service

5. Strangler-fig migration

The strangler-fig pattern peels functionality off a monolith incrementally, routing each slice to a new service instead of a big-bang rewrite.

strategy: strangler-fig-migration

A complete learning loop

Understand

Read the concept map and follow the code breakdown.

Reconstruct

Type the implementation, repair mistakes and work through every recall exercise.

Verify

Use the final check without hints; revisit weak concepts in short practice sessions.