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

Vertical Slice Architecture Myths You Need To Know!

As with anything that gains traction from a wider community, some misconceptions develop and spread. Vertical slice architecture falls into that trap. Don’t worry. I’ve got you covered to demystify some common Vertical Slice Architecture myths and why they likely exist. Let’s set the record straight. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. Share Nothing Easily, the biggest of the Vertical Slice Architecture myth is that you cannot share anything between features. That’s always the question I get in the comments. “How do I share… Read More »Vertical Slice Architecture Myths You Need To Know!

Google Service Weaver is a Bad idea

Writing distributed applications like microservices can be challenging. I know, surprise, surprise. Performance, versioning, testing, and the list goes on are all aspects that make it difficult. So there’s got to be an answer in the form of tooling that can make this easier. Maybe there is with Google Service Weaver? YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. Google Sevice Weaver Write your application as a modular binary. Deploy it as a set of microservices. https://serviceweaver.dev/ That’s the claim from Google Service Weaver. You split up your… Read More »Google Service Weaver is a Bad idea

Not everything is a service.

I need to create an email service within my system. The service’s responsibility is to send out customer emails for things like Order Confirmation or when Billing information is changed. But how do we communicate with this email service when we need to send an email? There’s another intuitive option that starts when you realize that not everything is a service. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. Event-Driven The first option would be using an event-driven architecture and the publish-subscribe pattern. In this scenario… Read More »Not everything is a service.