Skip to content

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.


Follow @CodeOpinion

Derek Comartin

Autonomous Services

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

Roundup #45: AWS Secrets Manager, Microservices, ASP.NET Core Architect, WCF vs gRPC

Here are the things that caught my eye this week in .NET.  I’d love to hear what you found most interesting this week.  Let me know in the comments or on Twitter. AWS Secrets Manager client-side caching in .NET AWS Secrets Manager now has a client-side caching library for.NET that makes it easier to access secrets from .NET applications. This is in addition to client-side caching libraries for Java, JDBC, Python, and Go. These libraries help you improve availability, reduce latency, and reduce the cost of retrieving your secrets. Secrets Manager cache library does this by serving secrets out of a local cache and eliminating frequent… Read More »Roundup #45: AWS Secrets Manager, Microservices, ASP.NET Core Architect, WCF vs gRPC

Context is King: Finding Service Boundaries through Language

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