Particular Software

Makers of NServiceBus and the most developer-friendly service platform for .NET … now also on the other site too

[Particular Software @ParticularSW]

We're now on the other site too! Follow us at https://t.co/Cl7FJxmfCV

[Particular Software @ParticularSW]

You can monitor your NServiceBus systems with @PrometheusIO and @Grafana using the code in this sample https://t.co/jcGIl0cR4J

[Particular Software @ParticularSW]

NServiceBus guarantees reliability and extensibility you just can't get with REST or other HTTP-based web services. Get a quick introduction to why building with NServiceBus makes building distributed systems better in our Quick Start tutorial https://t.co/xfFI6arF5F

[Particular Software @ParticularSW]

If you have a distributed software system and don't have the ability to replay a failed message, you're missing out. Check out our message replay tutorial to see just how powerful being able to replay a failed message can be https://t.co/njHQO4G7wL

[Particular Software @ParticularSW]

Boost your system’s reliability with NServiceBus's PostgreSQL transport. Enjoy seamless message queuing and processing. https://t.co/8M3vc2pc67

[Particular Software @ParticularSW]

Retries causing duplicates? Workflows breaking halfway? Services tightly coupled? Learn how to fix real microservice problems with https://t.co/a7UJeIihUt Core + NServiceBus 10. https://t.co/kKd8kZAelt

[Particular Software @ParticularSW]

Want to host NServiceBus in a #Docker container? Install the ParticularTemplates for dotnet new, and then call `dotnet new nsbdockercontainer` to create all the boilerplate you'll need https://t.co/j6F37oFpjx

[Particular Software @ParticularSW]

We need your input: Authorization is coming to ServicePulse and ServiceControl https://t.co/IgAQt0StX3

[Particular Software @ParticularSW]

How do you build complex workflows in message-driven systems? Our architectural guidance has you covered. https://t.co/TJlSXLH2ld

[Particular Software @ParticularSW]

No more "but it works on my machine." The same Aspire AppHost code runs locally during F5 and generates your production deployment artifacts. Your whole team gets the same dev experience. Your ops team gets the same definitions. No magic, no drift.
https://t.co/sNOrLPIm2I
#dotnet #Aspire #NServiceBus #distributedsystems #particularplatform #servicepulse #servicecontrol

[Particular Software @ParticularSW]

The N+1 Query Problem, Returning Full Entities Instead of Projections, Forgetting AsNoTracking on Read-Only Queries and more. What are the top 10 EF Core Performance Mistakes and How to Fix Them in .NET 10? Mukesh Murugan discusses in this article https://t.co/B7br60DhZB #dotnet #efcore

[Particular Software @ParticularSW]

Union types in C# 15 are currently in preview. Check out Maarten Balliauw's post on Discriminated unions in C# and .NET 11 that discusses this much awaited feature in great detail #csharp #dotnet https://t.co/6z0orgWf8I

[Particular Software @ParticularSW]

"We added a queue, so we're scalable now." Not necessarily. A queue removes temporal coupling. It doesn't magically solve load management. Without concurrency limits, a fire-and-forget message pump can create more problems than it solves. Daniel Marbach discusses how a message pump becomes an integral part of your architecture in the latest article.https://t.co/rTjUPzhejC

#dotnet #messaging #architecture

[Particular Software @ParticularSW]

"docker-compose up" was the old dance: waiting for containers, debugging port conflicts, fixing environment variables. F5 with Aspire does it in one shot. Code + infrastructure in one AppHost, one dashboard, one source of truth.
https://t.co/sNOrLPIm2I
#dotnet #Aspire #NServiceBus #distributedsystems #particularplatform #servicepulse #servicecontrol

[Particular Software @ParticularSW]

Clear insight into failed messages can make recovery work far less stressful. Retry failed messages with confidence using the Particular Service Platform https://t.co/13GVcqgu9q

[Particular Software @ParticularSW]

Is Event-Driven Architecture (EDA) actually a nightmare, or are we just using it as a scapegoat for poor system design? In this video, @codeopinion breaks down a common EDA "horror story" to show why the problems usually aren't the tech - they're the boundaries. https://t.co/0hQ5oTqZOs

[Particular Software @ParticularSW]

"PostgreSQL isn’t just a database—it’s a powerful messaging infrastructure for .NET apps.
Here’s why:
🔄 Coordinate workflows seamlessly with message-driven patterns
📊 Use atomic transactions across persistence & messaging
🚀 Scale distributed systems without additional infrastructure
Think beyond the DB. Learn how: https://t.co/DTTzTmxCfB
#PostgreSQL #DotNet #Messaging #Microservices https://t.co/bEWrQvhUc6"

[Particular Software @ParticularSW]

Use a SQL trigger to add a message to an #NServiceBus message queue when using the SQL transport https://t.co/npPsO64wWP

[Particular Software @ParticularSW]

Traces, logs, and metrics from your NServiceBus endpoints, ServiceControl, ServicePulse, and its database, all in one Aspire dashboard. No OpenTelemetry setup tax, no log aggregation config - they just flow together. One place to see your entire distributed system.
https://t.co/sNOrLPIm2I
#dotnet #Aspire #NServiceBus #distributedsystems #particularplatform #servicepulse #servicecontrol

[Particular Software @ParticularSW]

Remember when creating a distributed application meant stitching together containers, configuration, service discovery, health checks, and dashboards by hand? Aspire is changing that. A great overview of how Aspire is simplifying cloud-native .NET development and improving the developer experience for distributed applications. #dotnet #Aspire #CloudNative #DistributedSystems
https://t.co/ssH19DUtEI

[Particular Software @ParticularSW]

Your database says it happened. Your message broker says it didn’t. One system committed, the other didn’t, and now a customer is staring at a charge with no confirmation email - or worse, got the email for a charge that was rolled back. Two writes, no shared transaction, no guarantee they land together. The transactional outbox exists because this problem is unsolvable with retry logic alone. This article by Vivek Mittal discusses the transactional outbox pattern in great detail https://t.co/ijfxTZ1TZg