Udi Dahan

@udidahan.com

Posts about Software Development, Design, and Architecture. Founder and CEO of NServiceBus. He/Him. https://udidahan.com/ https://twitter.com/UdiDahan https://hachyderm.io/@udidahan

Modeling business requirements and policies is a tricky thing. In this video, @indualagarsamy discusses the saga message pattern to see how you can model complex business workflows, and model time as an immutable durable event

Evolving with the Changing Requirements: The DDD Dream

🔗Transcription 00:05 Indu Alagarsamy What I'm going to talk today, this talk is going to be, is requirements are going to be changing all the time and how can we keep up with those requirement…

particular.net

Another thing that’s sticking with me is the importance of social learning and peer support. I think I can credit a lot of my success, especially earlier in my career, to landing in an organization that values collaboration, information sharing, and mentorship.

How do you design a UI when the back-end system consists of dozens (or more) of microservices? In this video, Mauro Servienti shows how to use the concept of UI Composition to build a page without losing autonomy between services

Designing a UI for Microservices

🔗Transcription 00:01 Mauro Servienti So welcome again. And welcome to Designing a UI for Microservices. As said, my name is Mauro Servienti. So I'm a remote worker. So I'm fully working remotely for…

particular.net

If implicit ranking can silence a room of senior engineers during a training simulation, imagine what it is doing to your actual architecture design sessions. If we don't actively facilitate group dynamics and level the playing field, we lose the vital perspectives required to solve complex problems

This thread demonstrates how people may *think* they are representing the "problem space" when they are still subconsciously stuck in the "solution space". My recommendation is to delay naming things, using placeholders like colors in the interim - uncomfortable at first, yes, but helpful. Try it.

Kenny (Baas) Schwegler@kenny.weave-it.org · 9mo ago

We stop designing for the feature and start designing for the business problem. Coming up with new ideas and models to solve the problem. The takeaway: Name your bounded context towards the problems in the problem space, not the solutions in the solution space.

.NET 10 is out! Before you ask, you can already use .NET 10 in your #NServiceBus endpoints. We've run tests with the previews along the way to ensure you won't run into any issues when you change your target framework.

Announcing .NET 10 - .NET Blog

Announcing the release of .NET 10, the most productive, modern, secure, intelligent, and performant release of .NET yet. With updates across ASP.NET Core, C# 14, .NET MAUI, Aspire, and so much more.

devblogs.microsoft.com

Companies don’t realize their developers often make decisions without leadership involved (to build their own infrastructure because it’s fun) that then burden the company with supporting such systems indefinitely. At the expense of a simpler more maintainable app.

We can fall into a trap, believing things happen synchronously in a predefined order. They don't–at least not in scalable systems, and certainly not at Starbucks. "What Starbucks can teach you about (software) scalability" on our blog:

What Starbucks can teach us about software scalability

In 2004, Gregor Hohpe published his brilliant post “Starbucks Does Not Use Two-Phase Commit.” When I read it, my time working at Starbucks during my college years suddenly became relevant. Over the…

particular.net