Don't put client apps on the service bus. Find out how to deal with occasionally connected clients the right way.
Posts by Particular Software
Microservices are easy—until they need to communicate reliably. Join Roland Guijt on Pluralsight to learn how to build resilient microservices with NServiceBus, covering messaging, workflows, and the patterns real distributed systems depend on.
"It would be foolish to try implementing a service discovery scheme on your own when good options already exist, unless service discovery is specifically your business domain." The 5th Fallacy: Topology doesn't change, on our blog:
See how you can send #NServiceBus messages from an #ASPNetCore #WebAPI application. #samplecode
Stop organizing code by layers nobody thinks about. Start organizing by features everyone understands. Vertical Slice Architecture helps you build simpler, more maintainable .NET apps. Read more about this architectural style, when to use it, pros and cons in this article
Get up to speed on running #NServiceBus in a #Docker container. Check out the details of Docker hosting here
A consolidated view of messages makes patterns and anomalies easier to spot. See how teams review system-wide message activity using the Particular Service Platform
Your company acquired a competitor that uses the *other* cloud vendor? No problem. You can integrate any system using the NServiceBus.Transport.Bridge
Have you used a message queue before? See how NServiceBus makes building these systems faster and easier
Watch @mauroservienti show how to design a UI that effectively combines data from multiple microservices into one display in this webinar recording: All our aggregates are wrong
When one microservice fails, does everything fail? It shouldn’t. The Bulkhead pattern isolates failures so one problem doesn’t sink your entire system. A great .NET resilience pattern worth understanding.
It's 2am and messages won't process. Where are you going to turn? Get 24x7 critical support (even for MassTransit/Rebus/Brighter systems) with 5-hour or even 1-hour response SLA from the experts at Particular Software for as little as $1000 per month.
When a workflow becomes complex, it is easy to lose track of how messages actually move through each step. The Particular Service Platform flow diagram brings that movement into focus.
Synchronous calls optimize for simplicity. Messaging optimizes for reality. If you're building distributed systems in .NET, understanding queues, topics, and async communication is essential.
Did you know you can use #NServiceBus to receive #RabbitMQ msgs from any platform? Get the sample code!
File > New > Distributed system
Which AWS technologies are right for your distributed system? Our architecture guidance has you covered.
Learn how to use NServiceBus saga timeouts to model the concept of time without the need for unreliable batch jobs
In this video, @indualagarsamy talks about the intersection of #DDD as a software discipline with #messaging as a technology counterpart
See how to blend #SignalR and #NServiceBus when dealing with occasionally connected, transient clients in this sample
A missing config value won't stop your .NET service from starting. It'll silently break at 2 AM in production. IValidateOptions<T> with ValidateOnStart() prevents this: your service won't start with bad config, and the validator has full DI access for cross property checks. By Bart Wullems.
Have you looked at C# 14's extension members yet? You can now define extension properties, extension operators, and static extensions. It's the biggest change to how you extend types since extension methods shipped in 2007. Post by Dirk Strauss.
When a process crashes while holding a lock, what happens to the resource? Most teams don't find out until production teaches them. Chris Woodruff explores why indefinite locks are a liability in distributed systems and what to reach for instead.
Does your search need to understand meaning or just match exact text? That distinction is the core of what vector databases solve, and it's simpler than most explanations make it sound. Great walkthrough from @irina_scurtu.
Exceptions are a security boundary, not just a reliability concern. Your logs should have everything; your clients should have nothing they didn't need to know. Correlation IDs bridge the gap. Practical guide by Adrian Bailador.
In a theme park, you need to monitor how many people can ride a ride and which rides have the longest lines. Distributed software systems aren't much different! Maximizing fun (and profit) in your distributed systems, on our blog: