Beginner

Microservices Foundations

What microservices are, why and when to use them, communication patterns and how to adopt them.

When developing software, it starts small — a few features. But as features are added, complexity accumulates. When all this complexity stays in the same program, it's called a monolithic architecture — a monolith.

A monolith is not necessarily bad. A well-maintained monolith often has a modular architecture with abstractions that facilitate maintainability. But everything lives in the same application.

Microservices work differently: it's a collection of independent programs that collaborate to solve business problems, rather than having all business logic in the same program.

Sign in to read this course

A free account unlocks all 514 courses. 20 are readable without one.

What's inside

7 sections
  1. 1 Table of Contents
  2. 2 Module 1 — What Are Microservices?
  3. 3 Module 2 — Why Microservices?
  4. 4 Module 3 — Communication Patterns
  5. 5 Module 4 — Adopting Microservices
  6. 6 Architecture Diagrams
  7. 7 Reference Tables

Interested in this course?

Contact us to book it or get a custom training plan for your team.