Architecture

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

There are many misconceptions about CQRS. It’s often referenced alongside other patterns that can make it seem difficult and complicated. Is CQRS complicated? No. CQRS is simple. Really simple. What is CQRS? First, let’s tackle at the very core what CQRS actually is. CQRS stands for Command Query Responsibility Segregation and was coined by Greg Young. CQRS is related to CQS (Command Query Separation) principle by Bertrand Myer which states: Every method should either be a command that performs an action, or a query that returns data to the caller, but not both. In other words, a command is a… Read More »Is CQRS Complicated?