Distributed Monolith
How can a microservices based architecture, that looked great on paper, turn into a system that is a nightmare to maintain? Let’s have a look how well intended systems turn into a distributed monolith....
Tagged: architecture
Priority Queues – Interceptors
In the previous articles, I demonstrated why there is not really a need for priority queues. That is because the different messages likely need to be handled differently, both from the business- and infrastructure...
NDC London 2016 Distributed System Principles
In the eight fallacies, there’s one that says the topology never changes. Isn’t that covered by the other fallacies? Because we kind of try to use the network in a way that abstracts us...
Business Components as mini systems
In my High Availability article I mentioned business components and questions were asked in the comments, what these business components actually are. This post is a follow up to my previous post about the autonomy of...
LIDNUG Presentation on messaging
The LinkedIn DotNet User Group (LIDNUG) organisation requested me to do a Building Reliable Systems with Messaging session for them. This webcast was something quite new for me, because I’ve never presented anything without...
Autonomous Business Components
In my article on High Availability I mentioned business components. The most often asked question is what these business components exactly are. How big or small they are and what these business components contain....
Recent Comments