Feed

Note that I may not have fully read/viewed all of the things in this feed. The images, content and opinions in them are owned by their respective authors.

Modelling Bounded Contexts with the Bounded Context Canvas

Nick Tune - medium.com

How do we break a large system into smaller, more manageable modular components? This is the question I get asked the most, so I’ve put together this article describing a workshop recipe you can use…

How to Avoid Coupling in Microservices Design | Capital One

capitalone.com

In this article, I am going to focus on the importance of loose coupling as a design principle for microservices. I will give examples of poor design decisions that violate loose coupling and lead to distributed monoliths.

Don't keep a saga in both camps

milestone.topics.it

Recently I delivered a distributed systems workshop for an Italian user group. Based on some of the conversations I had with attendees, I wrote, “There is no...

Jeremy Miller - The Shade Tree Developer

gRPC - A Modern Framework for Microservices Communication

Harish Kathpalia - Capital One

High-performance remote procedure call framework

kamalraturi - https://gitmemory.com/

Just wanted to contribute my experience getting Funbuckle.MultiTenant to work with Blazor and Razor Pages on .NET Core 3.0. So far it seems to be working. Perhaps these instructions will help others.

[Ask Udi] Two services operating on the same entity

Udi Dahan - Udi Dahan – The Software Simplist

Most of my regular readers know that I recommend against having more than one service operating on the same entity, but with the groundswell of interest around microservices, there appear to be more and more people who are falling into this trap, so I thought it worthwhile to do a short refresher on the topic.