Fridays are great to watch a good talk… and this one by Gregor Hohpe is definitely worth your time! Architects are not supposed to be the smartest people in the room, rather, they make everyone else smarter, by connecting dots, sharing decision models and revealing blind spots… 👉🏼 https://lnkd.in/e5AZ2EK5 #softwarearchitecture #architectelevator #decisionmaking #criticalthinking
Particular Software
Software Development
Haifa, Haifa 3,088 followers
Makers of NServiceBus - the gold standard for async .NET microservices on Azure, AWS, and on-prem
About us
At Particular Software, it's not just about writing software and building great products. It's about improving the lives of the developers, tech leads, and operations professionals who drive the software industry. The software we develop helps organizations design and build elegant mission-critical systems by letting them focus on their business code instead of wasting their time reinventing the infrastructural wheels underneath it. It's also about working with exceptional colleagues with great work ethics, empowering you to continuously learn and grow, both professionally and personally. CEO and founder, Udi Dahan, sets the tone for challenging ourselves to craft an unrivaled product, provide the best customer service, and build the most agile and effective organizational structure. We ARE Particular. If you think you might be Particular too, check us out: http://particular.net/careers
- Website
-
http://particular.net
External link for Particular Software
- Industry
- Software Development
- Company size
- 11-50 employees
- Headquarters
- Haifa, Haifa
- Type
- Privately Held
- Founded
- 2010
Locations
-
Primary
Get directions
45 Berl Katzenelson Ste 73
Haifa, Haifa 34752, IL
Employees at Particular Software
Updates
-
A great post by Steve Gordon on how to #encrypt properties with the TypeInfoResolver Modifier in .NET! But remember, if your goal is to encrypt certain parts of your message payloads, #NServiceBus can do that encryption for you out of the box 😉 #encryption #security #dotnet #json
Blogged: Encrypting Properties with System.Text.Json and a TypeInfoResolver Modifier (Part 1). https://lnkd.in/gegrCh8X In this post we start creating a TypeInfoResolver modifier in System.Text.Json to encrypt and decrypt JSON properties during serialisation. #dotnet #json
-
Have you ever wondered how you can set up end-to-end observability for your .NET system on Azure? It’s not just classic Application Insights anymore. The shift to #opentelemetry fundamentally changed how we collect telemetry from systems. Check out this blog post that will walk you through it: https://lnkd.in/e5HVx_5M #o11y #azure #dotnet #azuremonitor
-
In addition to what Nick Tune said, don’t forget that AI agents will likely be calling other agents and services, also in parallel. We’ve been dealing with network issues, peak loads, concurrency and consistency in distributed systems for years, through queues! #distributedsystems #eda #systemdesign #ai #agents
If AI allows us to manage multiple agents working in parallel, then architecture becomes even more important. A tightly coupled architecture will block parallel development. A loosely coupled, modular architecture will facilitate it. #domainDrivenDesign
-
Have you ever needed to start a batch of tasks in a message-based sysem? Sagas can help you achieve just that. This pattern of throttled message generation can be helpful when the the rate of generation needs to be controlled. Check out the relevant use cases and full sample we have available for this topic! 👇🏼 https://lnkd.in/ejCWyUT5 #particularplatformsample #sagas #batching #eda #nservicebus
-
At NDC Conferences in Copenhagen, Jerry Nixon delivered a talk on modern architecture for new and forgetful engineers. He mentions something that’s often overlooked in message-based systems… If you introduce a service bus, you MUST also introduce dead-letter management. 💀✉️ Dead-letter management is a concern that doesn’t receive much attention, but is a critical part of any system that wants to maintain consistency in the face of persistent errors… And that’s exactly why we built the Particular Service Platform… So that once the web service is back up, or you’ve fixed that nasty bug, you can easily retry messages without having to manually figure out where to route them, potentially altering the message body before doing so! Check out the full talk: https://lnkd.in/eippNd38 #particularplatform #servicebus #deadlettermanagement #servicepulse #eda
Modern Architecture 101 for New Engineers & Forgetful Experts - Jerry Nixon - NDC Copenhagen 2025
https://www.youtube.com/
-
“Microservices is a physical architecture choice. That’s what you’re choosing when you introduce it. You’re introducing network boundaries. But regardless if you have a monolith or microservices, whether you’re a small team or not, the key is to define logical boundaries.” As Derek Comartin mentions in this post, the first step towards a successful design is defining the logical service boundaries. How you end up deploying the system is a completely different decision with different criteria! #serviceboundaries #logicalvsphysical #microservices #monolith #systemdesign
DHH had a take on microservices in small teams that is getting a lot of attention. And while I agree with what he’s pointing out, all of these types of conversations miss what actually matters. This is not about microservices, monoliths, or small teams. https://lnkd.in/g2xATqUr
-
“Modular monoliths give you the logical architecture of Microservices without the operational complexity. You can safely determine the boundaries between modules. And refactoring is straightforward and less risky. They can also be easily migrated into Microservices if you decide to do so.” Check out Milan Jovanović latest post on #synchronous versus #asynchronous #communication in the context of #modularmonoliths 👇🏼
Sync or async communication? It's an important decision in any architecture. Here are the tradeoffs in a modular monolith. Synchronous communication: - Directly calling the public API - Method calls or network calls - Easy to implement - Temporal coupling - No indirection Asynchronous communication: - The public API becomes a message - More complex, requires a message bus - Simpler migration to microservices - Easy to introduce new consumers - Eventual consistency You can see each approach has some pros and cons. So how do you choose? I wrote an in-depth comparison of the modular monolith communication patterns. Here's everything you should know: https://lnkd.in/eaVfhJE3 A personal preference: start with sync communication. We don't know what the module boundaries will be, and sync communication lets me refactor faster. --- Sign up for the .NET Weekly with 76K+ other engineers, and get a free Clean Architecture template: https://lnkd.in/e-PHgi4n
-
As the ecosystem continues to change and evolve, the .NET team continues to reinvent how .NET is built and shipped. From .NET's early days, born out of the closed source infrastructure of the .NET Framework and Silverlight, to multiple repositories that held CoreCLR, CoreFX, and CoreSetup, to repositories containing ASP.NET Core, EntityFramework Core, and an SDK with a CLI. This post on Microsoft's blog walks you through their pains, their needs and their learnings, leading to the current Unified Build system they've developed: https://lnkd.in/ebaSEBzG #dotnet #shipit #microsoft #buildrelease
-
Is your message coming from a valid sender? When integrating across systems, this is an essential check to ensure you're not ingesting malicious or malformed data. With #nservicebus, you can extend the processing pipeline to verify the message signature seamlessly. Check it out! 👇 https://lnkd.in/efyUG96N #particularplatformsample #messagesigning #verification #security #eda