Makers of NServiceBus and the most developer-friendly service platform for .NET … now also on the other site too https://xitter.cf/t.co/0d2pUHzYJK

Everywhere
Joined December 2012
💬 Last chance to meet the engineers behind @ParticularSW. If you're at #ndcoslo, share your architecture challenge. Bonus: While you're here, enter our raffle to win a LEGO Pac-Man Arcade. 👾 #dotnet #distributedsystems
168
Exploring a legacy codebase of your own? Or did @WilliamBZA 's Indiana Jones and the Temple of Legacy Code spark a few questions? 🤠 📍Continue the conversation with William at the Particular Software booth right after the session. If you miss him, stop by later; we'll help you connect. Come chat about legacy code, safe refactoring, testing, and modernizing existing systems. #ndcoslo #dotnet #legacycode #softwarearchitecture #testing
148
🗺️ Legacy code doesn't have to stay a mystery. Join William's #NDCOslo session "Indiana Jones and the Temple of Legacy Code" to explore practical techniques for understanding, testing, and safely evolving legacy systems. Plus, it's fun! And no snakes…probably. 📍 Room 5 | 🗓️ Thu | 🕜 1:40 PM #ndcoslo #dotnet #legacycode #softwarearchitecture #testing
162
Saw @noctovis's Change is inevitable: Versioning event-driven systems at #NDCOslo? Or couldn't make it? 📍 Meet Laila at the @ParticularSoftware booth right after the session or during lunch. Whether you have questions about message versioning, evolving event-driven systems, or event-driven architecture, she'd be happy to continue the conversation. #eventdrivenarchitecture #distributedsystems
1
149
💬 One question we've been discussing today at #NDCOslo: How long do you keep old event versions around? Curious how your team approaches it. Come join the discussion at the @ParticularSW booth.
147
Hey #NDCOslo! 👋 Meet the engineers behind Particular Software! @SzymonPobiega @PoornimaNayar @Masternak and Andreas are here. Building a #distributedsystems? Bring your architecture questions. We'd love to talk messaging, event-driven systems, reliability, and real-world trade-offs. #dotnet
3
329
Coming up at #VSLive - Hazel Bohon presents Microservices for Pragmatists📍 T08 | 🗓️ Tues, September 15 | 🕤 9:30AM vslive.com/events/san-diego-…
158
Thinking about microservices but worried about complexity? Microservices for Pragmatists📍 T08 | 🗓️ Tues, September 15 | 🕤 9:30 AM at #VSLive vslive.com/events/san-diego-…
2
199
In a distributed world, where we mix legacy and greenfield systems, getting them to agree becomes quite a bit more complex. Jimmy Bogard discusses various consistency and transactional patterns to support both real-time and async updates in this video youtube.com/watch?v=FZ-1dbtQ…
1
237
When you're building retail systems, scalability is a real concern. You need to be ready to handle seasonal traffic spikes, including Black Friday. Will you be ready? Learn a better approach to building retail systems with #NServiceBus particular.net/solutions/ret…
161
Just two snippets is all you need to get an NServiceBus solution working on #Aspire. See how! particular.net/blog/particul…
2
182
Saying 'no' to requests is how you stay alive under load. @irina_scurtu explains load shedding; the resiliency pattern that intentionally drops traffic to protect your system. #dotnet #distributedsystems irina.codes/load-shedding-dr…
2
288
Eventual consistency isn't a bug; it's a deliberate design choice. @irina_scurtu breaks down what it really means, when to embrace it, and how to reason about distributed state. #dotnet #distributedsystems irina.codes/eventual-consist…
1
180
“…as with any architectural choice, the other side of the coin surfaces challenges and pitfalls that we must consider” Messaging: The fine line between awesome and awful - @noctovis at @NDC_Conferences youtube.com/watch?v=phAaF6OG…
1
318
Afferent coupling, efferent coupling, platform coupling, spatial coupling, temporal coupling. Can you differentiate them all? If not, it's time to join @udidahan's free distributed system design fundamentals course! go.particular.net/l/27442/20…
2
247
The flow diagram shows how messages actually move through a workflow. On the Particular Service Platform, this helps clarify behavior and removes uncertainty around diagnosing issues. docs.particular.net/servicep…
170
To host multiple Azure Functions endpoint in a single app, you combine a ServiceBus trigger with a method to configure the endpoint, all in a partial class that lets our source generator wire up the details. particular.net/blog/multi-en…
1
1
194