Domain-Oriented Microservice Architecture
Depending on what angle you come at this from, you could say that DOMA groups services into clusters (&quot;domains&quot;), as Uber has done here, or that services always should have been domain-driven, and DOMA welcomes the networking layer inside the bounded context as well.<p>I&#x27;ve spent a lot of time trying to understand when a microservices architecture makes sense, what the caveats are, and what philosophy one should take to building services. All the material I&#x27;ve read seems to point in the direction of services being ideally coupled to domain boundaries.<p>It seems to me that Uber&#x27;s services proliferated beyond the framing of bounded contexts, and DOMA is their attempt to reign it back in again. I think it&#x27;s an excellent strategy, and arguably a very good approach for other companies who find themselves in this position.<p>I don&#x27;t think DOMA is a good place to <i>stay at</i>. The network should only be tolerated as long as it provides benefits that outweigh the costs. &quot;Monolith&quot; is not synonymous with &quot;poor design&quot;. Seeing that these enclaves of services sitting within a domain depend on eachother in the way the OP describes, it really makes me think that they&#x27;d find further benefits by expelling the network from each domain.