I enjoy designing distributed systems using event-driven architecture style and domain-driven design principles. I have over 15 years of software development experience working with various industries like healthcare, finance, biotech, and emergency services.
I am currently a Distributed Systems Engineer at Particular Software, the makers of NServiceBus. I am passionate about diversity and inclusiveness in the tech industry. When not programming, I am an occasional rock climber, who loves to chill in sunny Southern California with my kids and super chill giant mastiff.
Resilience Design Patterns
How does your system react when a key resource fails? Say, the database becomes unavailable, or the message broker fails. What if you get a current surge of load, that you have to keep up? What if a badly worded error message results in a billion dollar fire.
Real life engineering disciplines can teach us a thing or two on designing for resilience.
Learn the techniques and patterns that you can borrow from other areas of engineering, and apply them in your systems.
Using the Saga Pattern
Modeling business requirements and policies is a tricky thing. Especially when those requirements just keep on changing. Sure, we’ve all written code before to model requirements, but how can we achieve the dream of evolving the code and at the same time be aligned with the business?
We can use the Saga pattern to evolve crucial business policies. We can even model time as a durable event to keep our code resilient.
In this session, we’ll code the saga message pattern to see how you can model complex business workflows in such a manner that it truly evolves around your business.