Figure 4-13 Multiple application ownership boundaries part of a single domain Figure 4-14 Microservices capabilities made available via APIs - 1 Chapter 4. Cloud-native concepts and technology  117 How can consumers find the APIs they want from the overwhelming set available? Which are  APIs that should be re-used in other contexts? Ideally microservices components are completely independent. But, in reality, some are really  used only in the narrow context of an application. And some others are intended for much  The agreed-upon definition of an application boundary also allows to take a close look at the  APIs that are exposed by each application component, for simplicity identified as a  microservice. Most microservices components make their capabilities available via an  interface such as RESTful HTTP/JSON based APIs. Just as the number of microservices  components on the network increases, so does the number of exposed APIs on those  components. See Figure 4-14 on page 117. Ž ŵ Ă ŝ Ŷ  Ž ŵ Ă ŝ Ŷ  $ S S O L F D W L R Q E R X Q G D U \ $ S S O L F D W L R Q E R X Q G D U \ $ S S O L F D W L R Q E R X Q G D U \  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H $ S S O L F D W L R Q E R X Q G D U \  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H $ S S O L F D W L R Q E R X Q G D U \  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H $ 3 ,  6 H U Y L F H 0 L F U R V H U Y L F H F R P S R Q H Q W  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H  6 H U Y L F H