🚀 Finding Your Service Boundaries – A Practical Guide (Adam Ralph)

A practical guide to finding your service boundaries, bringing clarity to the blurry lines between separate services.

Key takeaways

Services are a complete encapsulation that shares no data.
Amazon’s architecture is designed to be called by other microservices.
Microservices are vertical things, not horizontal.
The physical boundary is a service boundary and it is a logical boundary.
It’s not the entity, it’s the field.
Services are supposed to help, not hinder.
Loosely coupled services are better than tightly coupled ones.
The business domain is where service boundaries are drawn.
Service boundaries are not technical boundaries.
You can roll out 10, 20, or all of them at the same time.
Systems are physical runtime concerns, not logical concerns.
Data access was very cheap in Amazon’s architecture.
Finance says, “Ah, yeah, you told me during the workflow”.
Sometimes it’s just a case of having the right tools.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll out 10, 20, or all of them at the same time.
The business knows what they don’t want.
It’s not about nouns, it’s about behavior.
You can’t sweep stuff under the carpet.
Loosely coupled services are better than tightly coupled ones.
It’s not about modeling, it’s about encapsulation.
The business domain is where service boundaries are drawn.
Services are a logical concept, not a technical one.
Loosely coupled services are better than tightly coupled ones.
You can roll

🚀 Finding Your Service Boundaries – A Practical Guide (Adam Ralph)

More talks