Logical Architecture Solution 1 ... Application 1 ... Solutions: provide new business capabilities Solutions/ Applications Decoupling Layer: enable full access to all data Domains Business Services Decoupling Layer Microservices Domain 1 Domain 2 Domain 3 ... Domains: set of data entities supporting a set of business processes Data Domains Rules Solutions cannot interact with microservices Microservices cannot interact with each other (but they can send and consume events in/from a queue) Business services can consume and send events from/in queues and call multiple microservices Experiences and Tips Microservices and Business Services deployed on EKS With so many microservices and business services it's essential to have a service discovery system (EKS helps for this) The publication of swaggers is essential Staffing effort can be challenging Domains are more than Solutions Sidecar pattern for microservices Important: I don't recommend an implementation of this approach as is, I think it is useful to get the idea behind and implement things incrementally and only when it becomes necessary, then implement complex features like service discovery or things like that