🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
[Blog post for developers] Using Delayed Delivery Queues in Your Event Mesh to Implement Timers
When building an application using a microservices architecture, it is much easier to horizontally scale those microservices – i.e, adding more service instances on demand – when those microservices are stateless. However, implementing timers can be a challenge. How can you “set aside” an event to be processed later, perhaps by a different instance of the microservice, without storing processing state in the microservice? The answer is to use a delayed delivery queue in your event mesh.
In this blog post, Steve Buchko, Solace’s VP of Product Management, Core Products, explores two scenarios in an e-commerce application example where delayed delivery queues really come in handy:
- Retrying processing after a time delay. I’ll use a credit card purchase authorization in an e-commerce application to illustrate this use case.
- One event, published to the event mesh, processed by different microservices at different times
Read the whole blog post here.
Have questions and comments about the blog post? Leave them below.
