This has been one of our main tenets with NServiceBus and the rest of the platform in Particular. Everything should always Just Work™.

"Rants and Raves" from @ShawnWildermuth > I think this is true whether it is an open source project, or a commercial product. It has felt like developers can get focused on “How hard could it be?”.

Proud #dotnetconf sponsor here 🙌 Don’t miss your shot at the epic swag — e-books, Amazon Gift Cards, training courses & more! Enter today 👉

NSB now completely *free* for orgs under $1M ! PLUS significant discounts as you grow to $5M !! https://t.co/rGFkG9rlAh

New in NServiceBus! Now you can use #CloudflareR2 to store large message bodies in #AmazonSQS systems, which may be more cost effective for your system.

A lot of really cool AWS .NET enhancements for NServiceBus. I especially appreciate the support for our Lambda Annotations framework. https://t.co/ZRKRWiP8az

It just keeps getting better and better...

@Aaronontheweb "And when your realise just how many edge cases there are, and it's gonna take 3-5 years to stabilise, you're gonna double-down?" "Triple down, if anything".

Earth is calling again. The Powerhouse Museum and MIT are inviting everyone to record a message to be beamed into space. What would you say to the universe?

@apxltd Higher-level abstractions like MT and NServiceBus get a lot of use + commercial traction because they solve real problems even over just a single transport type

"So you're mad that MassTransit is going to cost 4-5 figures going forward" "That's correct, Dave" "And so your team of 8 is rewriting all messaging using the raw RabbitMQ drivers?" "Correct" "At an estimated salary/time expense of $950,000 in upfront dev cost?" "Correct!"

"We are the Borg. Your messages have failed and will be assimilated. Resistance is futile." For Star Trek day this year, learn how to use the Borg's resiliency as an advantage using ServicePulse to manage when messages fail.

I recently came across a team using an LLM to implement a state machine. They called it "agentic". They also told me it worked correctly most of the time. I asked them to write down the list of rules for moving from one state to another. They listed them out. It didn't take

@codeopinion You don't need to use bare-bones SDKs or hand-roll your own abstractions and tools.

@codeopinion It's the same for dealing with dead-letter queues. Using bare-bones Kafka, yeah, that's hard. NServiceBus or MassTransit with RabbitMQ, Azure ServiceBus, or Amazon SQS - you get all the visibility and tooling you need: https://t.co/Nat6a1gJbl

@codeopinion If you're not using some kind of framework like NServiceBus or MassTransit, it can be hard to test more complex message-driven logic. With those kinds of frameworks, no biggie: https://t.co/krHC4s94lO

@codeopinion As he says, one part of it is very much a tooling issue. Things like not being able to see the flow of asynchronous events across multiple publishers and subscribers. Appropriate auditing/telemetry helps with that: https://t.co/BQF1lGNDGg

“We switched to Event-Driven Architecture... and now we can’t debug anything.” @codeopinion unpacks the various ways EDA goes wrong. https://t.co/G4hBWZ3q6m

Day 2 at #NDCOslo⚡️Come find us at our booth to chat about messaging patterns, service-oriented architecture and all things messaging related.

Stop exposing your DB over HTTP. CRUD APIs are not a good design. Messaging and task-based UIs lead to better boundaries and maintainability. Read more from this post by @CodeOpinion.

Don’t miss @dvdstelt at @dotnetdaysro ! Implementing the planet’s largest e-commerce site in vertical slices. Learn how to find service boundaries & build maintainable, decoupled systems. Room 1 | 10:50 #microservices #softwarearchitecture

May the 4th be with you https://t.co/FNoWLwsARj