This 👆🏻big time!

I come back to this repo from time to time. Have it bookmarked actually :)

Speedy recovery !

Thanks for sharing ! I loved these posts showing how business world differs from software world.

udidahan.com/2010/08/31/r...

Exactly my point I was sharing internally yesterday

So this is part of Azure Service SDK ? What about scenario when message handlers need to appear under the “span” that sent the message ? E.g. service A sends bunch of messages to be processed and Service B processes these messages. Wouldn’t this help to group these spans under the parent ?

While all of them are interesting, I’d pick setting up to move modules out later & orchestration/choreography between logical modules. I think first one is important given pace of change and need to adapt. Second, I’d love to see how logical module boundaries are defined & integrated.

Curious how those modules came to be ? Are they themselves bounded context(s)? What’s the decomposition principle?

My mental model of a service is “technical authority over business capability” (SOA). Microservices then break it down to smaller autonomous parts. So quite often they end up being process view.

So in a way you’re saying that microservice is a logical boundary, which physically could be broken down to smaller pieces (kafka consumer, ETL process etc) ?

Tbh I was always surprised how espn keeps him as an analyst/commentator. No wonder a lot of people were calling him names (for his “professional” opinions). Now this… smh

Would you mind sharing few of those challenges ?