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

Architecture

The Bulkhead Pattern: How To Make Your System Fault-tolerant

Keep one small part of your system from taking down the entire system. Let’s look at the bulkhead pattern, the various ways you think about it, and how it applies to your architecture, which will help you with fault tolerance to keep your system running. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. Problem With a large system, it’s easy for one part to affect the performance of other parts. This is true for monoliths but also for more distributed service-oriented systems. Most systems have heavily… Read More »The Bulkhead Pattern: How To Make Your System Fault-tolerant

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

Event-Driven Architecture lost its way

Event-driven architecture is excellent for decoupling—or is it? The industry is trending towards losing the value of decoupling because of how it uses and defines events. Let me explain so you can avoid getting caught up in the same coupling trap. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. Events I’ve been seeing events defined in four ways in the industry right now: in terms of size, they are either coarse or granularity and are derived from CRUD and data-centric or business-focused and behavior-centric. Coarse events… Read More »Event-Driven Architecture lost its way