System Design Notes
  • The Art of Scalable Systems: Designing for Success
  • BASICS
    • Key Characteristics of Distributed Systems
    • DNS
    • Load Balancer
    • API Gateway
    • Caching
    • Message Queues
    • Proxies
    • Databases
    • ACID
    • CAP Theorem
    • PACEL Theorem
  • System Design patterns
    • Bloom filters
    • Consistent hashing
    • Quorum/Consensus
    • Leader and Follower
    • Write-ahead Log
    • Segmented Log
    • High-Water Mark
    • Locking Lease
    • Checksum
    • Vector Clocks
    • Liveness
      • Heartbeat
      • Gossip Protocol
      • Phi Accrual Failure Detection
    • Split Brain with Generation Clock
    • Split Brain with Fencing
    • Resyncing Nodes
      • Read Repair
      • Merkle trees
      • Hinted Handoff
  • DATA SYNCHRONISATION PATTERNS
    • Two-phase commit (2pc) Pattern
    • CQRS
    • Saga
    • Transactional outbox
    • Change Data Capture (CDC)
  • Monolith Decomposition Patterns
    • Monolith vs Microservices
    • Motivation
    • The Strangler Fig Migration Pattern
    • Domain-Driven Design
    • Other Approaches
  • WHEN IN PRODUCTION
    • Metrics
  • SD INTERVIEWS
    • System Design Interview Template
  • REAL WORLD SCENARIOS
    • Design a Distributed Message Queue & Event Streaming Platform
  • 💰Payments Services
    • Parties: Acquirer, Issuer
    • Events: Chargebacks, Reversals
  • 🛣️Infrastructure
    • K8S - ClusterIP vs NodePort vs LoadBalancer
Powered by GitBook
On this page

Was this helpful?

  1. Monolith Decomposition Patterns

Motivation

PreviousMonolith vs MicroservicesNextThe Strangler Fig Migration Pattern

Last updated 2 years ago

Was this helpful?

Microservices have been getting more and more popular in recent years, and several companies are migrating monolithic applications to microservices. But just a reminder that switching to microservices might not always be the good option. Martin Fowler wrote a nice article regarding the . Here are a couple of useful statements:

  • Almost all the successful microservice stories have started with a monolith that grew too big and was broken up.

  • Almost all the cases I’ve heard of a system that was built as a microservice system from scratch, it has ended up in serious trouble.

monolith-first approach