September 2017
Intermediate to advanced
93 pages
2h 8m
English
Content preview from Designing Autonomous Teams and Services
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 3. Analyzing Domains
The heart of software is its ability to solve domain-related problems for its user.Eric Evans
After articulating your business strategy, the journey to autonomous teams continues by learning how to identify cohesion in your problem domain—finding concepts that change together for business reasons. Aligning teams and software systems with domain cohesion minimizes organizational and technical dependencies—the holy grail of autonomy.
Learning how to analyze your domain involves looking for patterns and abstractions. Just like software can be reasoned about as patterns and abstraction so can problem domains. In this chapter, you’ll see some of the most prominent patterns used for reasoning about domains, including subdomains, business processes, and user journeys. You’ll start to see the trade-offs involved in deciding which of these constructs you should align your teams and software with. In the next chapter, you’ll then learn practical techniques for discovering these constructs in your domain, and designing your teams and code around them.
Finding Domain Cohesion
Relationships exist between concepts in your domain. Concepts with the strongest relationships change together most often and, therefore, represent raw domain autonomy. Take the real-estate domain for example; living room space and outdoor space have a strong relationship because they describe different physical attributes of a property. However, the concept of a purchase date relates ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.