Jan 10 · 5 min read · Series: Designing a Microservice-Friendly Datahub In event-driven systems, failure is not an edge case—it’s the default state waiting to happen. Networks drop packets. Services restart. Code contains bugs. Messages arrive twice, late, or malformed. T...
Join discussion
Jun 18, 2024 · 1 min read · Use Dead Letter Queues to save event invocation data Serverless architectures rely heavily on asynchronous communication between functions and services. This often creates points of failure which can leave processes in an incomplete state when messag...
Join discussion
Mar 9, 2024 · 5 min read · Message Queues are just like queue data structures, it works on the principle of FIFO i.e. First in first out. Order is essential inside the queue. Let us take a practical example of an E-commerce website like Amazon suppose we perform two operation...
Join discussionOct 13, 2023 · 5 min read · At Togai, we have a microservices architecture. When some specific events happen, we push the event information to a message broker (NATS) so that other services that are interested in the event can consume it and do its work/processing. Whenever the...
Join discussion