Architecture

In my previous post, I explored how words and language used by users of our system in our domain space can have different meaning based on their context. This establishes which services own which behavior and data. In this post, I’m going to explore why services are autonomous and how we can communicate between them This blog post is in a series. To catch up check out these other posts: Context is King: Finding Service Boundaries Using Language to find Service Boundaries Focus on Service Capabilities, not Entities 4+1 Architectural View Model Autonomy Autonomy is the capacity to make an informed,… Read More »Autonomous Services

I’ve found that one of the most important ways to find service boundaries is through the dialog you have with various end users in different parts of the system we are working on. Really focusing in on the words they use can be instrumental in finding service boundaries. This blog post is in a series. To catch up check out these other posts: Context is King: Finding Service Boundaries Language Autonomous Services Focus on Service Capabilities, not Entities 4+1 Architectural View Model Taken out of Context If a statement or remark is quoted out of context, the circumstances in which… Read More »Context is King: Finding Service Boundaries through Language

Having explicit service boundaries is one of the tenets of SOA. Defining correct services boundaries is critical. I believe it’s one of the most important aspects of developing a system is finding service boundaries and it’s also really easy to get wrong. This blog series is intended as a guide for finding service boundaries within a domain for the system you’re developing. Finding Service Boundaries through Language Autonomous Services Focus on Service Capabilities, not Entities 4+1 Architectural View Model What’s a Service? Before I get too far ahead, I better clarify what “service” means to me so we can be… Read More »Context is King: Finding Service Boundaries