Microservices·Microservices essentials

Boundaries

A service should own a business capability and its data.

Advanced 10 min read Lesson 1 of 150 Challenge included
What you will be able to do
  • Split by capability, not by layer.
  • Keep data private.
  • Avoid distributed monoliths.

In plain English

A service should own a business capability and its data.

  • Split by capability, not by layer.
  • Keep data private.
  • Avoid distributed monoliths.
boundaries.txtText
good: billing, catalog, identity
bad: controllers service, models service
Your turn

Explain it back

Easy

Answer from memory: What should a service own?

TEXT · starter
Your answer…
Check your understanding before moving on.
Knowledge checkQuestion 1

What should a service own?

Select an answer to continue
Study tools

Make it yours.

Keep a private note for this lesson, then turn the key ideas into flashcards you can revisit.

Sign in to save notes and flashcards.Both are private to your account and stay with your progress.
Sign in
Finished reading?

Lock in what you just learned.

Mark this lesson complete to save your place and move one step closer to the certificate.

Next: Communication
Lesson 1 of 150 · 0% of course