Make your existing system reliable using messaging with #NServiceBus and SQL Server. It's an elegant way to introduce messaging concepts into a legacy application.

Every IBM MQ project reinvents the same plumbing. MQGET loops. Backout logic. Connection management. Every project writes the same infrastructure code, just slightly differently each time.

Maybe you've heard about the fallacies of distributed computing. But if you want to understand them in more detail, join @udidahan's Distributed Systems…

Monolithic customer models create tight coupling and performance issues in distributed systems. @KijanaWoodard argues for team-specific data views to reduce bottlenecks and cognitive load

HTTP APIs aren't the only way to integrate systems with different technologies. NServiceBus Messaging Bridge allows direct asynchronous communication and decoupling between systems that use different transports.

Check out our guidance on selecting the message transport for your NServiceBus system. Includes detailed information and a handy decision chart

Transactions between your sagas and business data made possible with #AzureCosmosDB ☁️ #NServiceBus

Union Types are here in C# 15 and it looks genuinely exciting. For years we've modeled “one of many possible outcomes” using inheritance hierarchies, marker interfaces or lots of…

Seeing all message activity in one place changes how you debug. The All Messages view in the Particular Service Platform makes that possible

"No way would a 'real' developer be caught dead using 'windows' on their character-mode terminal, no way. It was vi or nothing. Er, sorry, I meant emacs. vim. OK, whatever editor you chose to use, you used that editor, then shelled…

Businesses can adapt to out-of-order delivery of information so our software should be able to as well. Otherwise pizzas could only be delivered one at a time, and might get cold if the driver got lost on the delivery before you.

Idempotency in distributed systems is the property that saves you after the network lies, the queue retries, the client panics, and the operator hits replay. In production systems, duplicate delivery is normal. Duplicate side effects are the bug.

Carl and Richard talk to Dylan Beattie about the Use What Works movement, encouraging developers to use well-maintained open-source projects available today rather than rolling their own.

Sagas are powerful tools, but they're not ALL-powerful. When your process involves an external source of truth, the missing piece is reconciliation.

Model Context Protocol (MCP) servers are becoming a key part of how Claude Code extends its capabilities. They give the agent access to documentation, code…

If you're interested in the idea of vertical slices and ViewModel composition, you should check out ServiceComposer, which now includes OpenTelemetry support!

In this video, learn from @adamralph how to turn the remote working dial up to eleven. All you need is a laptop, a camper van, some SIM cards, and a thirst for adventure.

Small code paths become expensive when cloud workloads execute them millions of times. The Azure Event Hubs partition key resolver is one of those paths. By…

IBM MQ is point-to-point. Pub/sub is a manual wiring job on the queue manager. There's no "publish an event and let subscribers handle it" model in the native client. Topic objects and durable subscriptions have to be configured…

In a web application, you probably just want to send NServiceBus messages without processing any or maintaining a queue. This sample will show you how to get that set up in an #AspNetCore WebAPI application.

Whether you are a seasoned architect or a developer just starting to explore DDD, understanding how to communicate between different parts of your system via events is a superpower.

If web development is your thing, here's one for the calendar. @csharpfritz is teaching a hands-on livestream workshop on modern web development. Practical, current, worth your time. We're proud to support it.

We've released a new version of our Azure Service Bus transport that supports dead-lettering and DLQ auto-forwarding among other improvements.

"We need to embrace the idea that some failures are inevitable. It's too expensive to try to prevent them completely. Instead we should focus on making sure we can detect issues quickly and compensate for them when they arise."

A useful reminder from Milan Jovanović: primary constructor parameters are captured as mutable variables, not readonly fields. The compiler will not stop you from reassigning them. In service classes that is rarely a real bug; in entities it can be.

NServiceBus allows you to focus on the domain logic and not the infrastructure code required to deserialize messages and invoke your business code on AWS Lambda.

Retries causing duplicates? Workflows breaking halfway? Services tightly coupled? Learn how to fix real microservice problems with ASP.NET Core + NServiceBus 10.

Using #antirequirements is a powerful way to increase autonomy by breaking your domain into separate islands that can evolve independently. Learn how to use anti-requirements in your system design in our blog post.

A big thank you to the event organizers of #TechoramaBE, you pulled off another great edition of the event. A big thank you to everyone who came to the Particular Software booth. We loved talking all things messaging to you all. See you all at #TechoramaNL later this year.

Monitor all your systems together by exporting your NServiceBus message processing metrics to @NewRelic. This sample will show you how

Most real bugs in #dotnet services live at the seams, between handler and unit of work, between #EF Core and #PostgreSQL, between HTTP and authorization. Unit tests with mocks rarely catch them. Milan Jovanović explains why he changed the testing shape he ships with.

When a rule about your domain has to hold true every time you touch the object, why does it usually live in a validator, a handler, or a controller instead of on the object itself? Milan Jovanović on invariants and where they actually belong.

In this video, @indualagarsamy talks about the intersection of #DDD as a software discipline with #messaging as a technology counterpart

All good things must come to an end and so does our time at #TechoramaBE. A big thank you to the event organizers, sponsors and the attendees. Thank you for the great talks, wonderful conversations and learnings. See you all at #TechoramaNL in October.

"This is the difficult leap of queueing technologies: not that they have an API that is difficult to use (they don't), but that they require letting go of more traditional request/response programming models." The network is reliable, on our blog:

We are excited about this session from Clemens Vasters at #TechoramaBE. Learn from the lead architect of Azure Messaging himself on how Azure Service Bus is built and powers everthing from your airport check-in to unlocking your car with a mobile app

Event-driven systems aren’t hard - until you need to change them. @lailabougria is up next in Room 8 talking about practical techniques to evolve safely, maintain compatibility, and ship changes without downtime. #TechoramaBE

OpenTelemetry promises better observability—but getting there isn’t easy. Where do you start? Jimmy Bogard will speak to you in Room 8 on how to adopt OpenTelemetry in brownfield systems with practical strategies from code to production at #TechoramaBE

Why is Output Cache still one of the most underused tools in #AspNetCore Core? A clear writeup from Anton Martyniuk on how it differs from object caching, where it earns its place, and the safety problem you have to solve before turning it on for authenticated APIs.

Why has it taken this long for C# to get a closed set of return types with exhaustive pattern matching? Good overview from Bill Wagner on what union types in C# 15 are trying to solve and what designs they make possible that traditional hierarchies cannot express.

Duplicate messages spreading through your system like wildfire? The Outbox pattern helps, but many implementations come straight from the Dark Ages, crushing your database. Szymon will help you evolve your Outbox in Room 7 at #TechoramaBE.

Modern .NET service workloads need to keep latency low even as data sources expand and external calls multiply. Jared Meade walks through the cache layer problem and why a tiered approach matters when in memory alone is volatile and a remote cache alone adds round trips.

Pub/Sub is where most systems start. What happens when messages are lost, duplicated, or workflows stall? @PoornimaNayar has answers to these questions in her upcoming session at #TechoramaBE in Room 9. You don't wanna miss it!

Visit our booth and grab your copy of "Exceptions and ACKs" game. Play with your team mates and see who is the master of throwing others into exceptional situations. Don't worry. With NServiceBus, exceptions are harmless and messages can be retried. #TechoramaBE

"Step forth, traveler Visit the Particular Software booth #TechoramaBE: tales of messaging… and treasures to be won 🪙 Only the curious shall leave with swag 🏰"

"Brave developers of TechoramaBE - venture to the Particular Software booth. Trade tales of lost messages and broken workflows for better messaging. Riches? No. Better - reliable systems. #TechoramaBE"

Every custom solution your team builds is a solution your team must maintain forever. Chris Woodruff makes the strategic case for why so much engineering budget gets quietly burned on infrastructure problems other people have already solved.

Question for teams running .NET on Azure: how much of your local dev pain is from mocking Azure services that have no real emulator? A useful comparison piece by Kamil Mrzygłód on closing that gap.

Most distributed systems don't fail in design — they fail in production. And these sessions at #TechoramaBE this year will help you tackle that futureproof your systems.

Order processing slides into inventory updates, email notifications, and loyalty calculations all in one transaction, and the codebase quietly turns into a big ball of mud. Sarah Dutkiewicz's recap covers using domain events so core entities stop knowing who is listening to them.