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

Roundup #46: .NET Core 1 EOL, EF Core 3.0, WCF OSS, Hidden Gems in .NET Core 3

Here are the things that caught my eye recently in .NET.  I’d love to hear what you found most interesting this week.  Let me know in the comments or on Twitter. .NET Core 1.0/1.1 End of Life Link: https://dotnet.microsoft.com/platform/support/policy/dotnet-core Entity Framework Core 3.0 Preview 6 and Entity Framework 6.3 Preview 6 In recent months, a lot of our efforts have been focused on a new LINQ implementation for EF Core 3.0. Although the work isn’t complete and a lot of the intended functionality hasn’t been enabled, before preview 6 we reached a point in which we couldn’t make much more… Read More »Roundup #46: .NET Core 1 EOL, EF Core 3.0, WCF OSS, Hidden Gems in .NET Core 3

Focus on Service Capabilities, not Entities

One of the most common pitfalls I think I’ve fallen into is focusing too much on data entities rather than service capabilities. What tends to happen is building up a domain model of behaviors related to single entities. As I’ve mentioned in my post about using language to find service boundaries, you can have the same entity that lives in a different context, but that owns specific behaviors and data. This blog post is in a series. To catch up check out these other posts: Context is King: Finding Service Boundaries Language Autonomous Services 4+1 Architectural View Model Entities I’m… Read More »Focus on Service Capabilities, not Entities

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