--- title: "#event-driven-architecture articles | Hashnode" description: "Explore 442 articles tagged #event-driven-architecture on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/event-driven-architecture" --- Tag # #event-driven-architecture 442 posts · 66 followers [M Antony](https://hashnode.com/@mercyantony) · [Nov 3](https://hashnode.com/posts/event-driven-retail-integration-connecting-erp-pos-and-ecommerce/6aea4aa5179e200a7ed50431) ### [Event-Driven Retail Integration: Connecting ERP, POS, and Ecommerce](https://retailtechinsights.hashnode.dev/event-driven-retail-integration-connecting-erp-pos-and-ecommerce?utm_source=hashnode&utm_medium=feed) Design a retail event pipeline with JSON contracts, PostgreSQL outboxes, and versioned stock updates that hold up under retries. 5 min read · [retailtechinsights.hashnode.dev](https://retailtechinsights.hashnode.dev/event-driven-retail-integration-connecting-erp-pos-and-ecommerce?utm_source=hashnode&utm_medium=feed) [Will Peixoto](https://hashnode.com/@willpeixoto) · [Oct 29](https://hashnode.com/posts/eventbridge-new-custom-event-bus/6ae3354d5972791246eedf36) ### [New EventBridge Custom Event Bus vs SQS FIFO: when to switch](https://willpeixoto.dev/eventbridge-new-custom-event-bus?utm_source=hashnode&utm_medium=feed) New EventBridge Custom Event Bus: RAM sharing, replay and FIFO by EventGroupId. When it takes SQS FIFO out of your integration, and when it doesn't. 19 min read · [willpeixoto.dev](https://willpeixoto.dev/eventbridge-new-custom-event-bus?utm_source=hashnode&utm_medium=feed) [Will Peixoto](https://hashnode.com/@willpeixoto) · [Oct 27](https://hashnode.com/posts/invisible-coupling-distributed-monolith/6ae0928b630ccbf172cdc0fc) ### [Invisible Coupling: When Your Microservices Become a Distributed Monolith](https://willpeixoto.dev/invisible-coupling-distributed-monolith?utm_source=hashnode&utm_medium=feed) Synchronous call chains turn microservices into a distributed monolith. How temporal coupling costs you p99 latency, money and resilience. 13 min read · [willpeixoto.dev](https://willpeixoto.dev/invisible-coupling-distributed-monolith?utm_source=hashnode&utm_medium=feed) [Madhav Bhasin](https://hashnode.com/@madhavbhasin) · [Oct 16](https://hashnode.com/posts/what-i-learned-running-real-time-pipelines-at-scale/6ad270bb8ac87fa77d407335) ### [What I Learned Running Real-Time Pipelines at Scale](https://blog.madhav.dev/what-i-learned-running-real-time-pipelines-at-scale?utm_source=hashnode&utm_medium=feed) Seven lessons from building and operating real-time event pipelines at scale — the things that weren't in any tutorial 7 min read · [blog.madhav.dev](https://blog.madhav.dev/what-i-learned-running-real-time-pipelines-at-scale?utm_source=hashnode&utm_medium=feed) [7](https://hashnode.com/posts/what-i-learned-running-real-time-pipelines-at-scale/6ad270bb8ac87fa77d407335) [Anakin Tech](https://hashnode.com/@anakinwriters) · [Oct 9](https://hashnode.com/posts/real-time-intelligence-fails-when-it-streams-noise-instead-of-decisions/6ac8bc4df8f5af5b888482a0) ### [Real-Time Intelligence Fails When It Streams Noise Instead of Decisions](https://anakinwriters.hashnode.dev/real-time-intelligence-fails-when-it-streams-noise-instead-of-decisions?utm_source=hashnode&utm_medium=feed) Real-time market intelligence fails when teams stream observations instead of modeling decisions. Build versioned state, material events, and guardrails. 7 min read · [anakinwriters.hashnode.dev](https://anakinwriters.hashnode.dev/real-time-intelligence-fails-when-it-streams-noise-instead-of-decisions?utm_source=hashnode&utm_medium=feed) [Usman Khan](https://hashnode.com/@usmankhan-io) · [Oct 3](https://hashnode.com/posts/microservices-event-pipelines-outbox-pattern-cdc/6ac0e7e8ecfecca894b55055) ### [Microservices Event Pipelines: Outbox Pattern, CDC, and Idempotent Event Sourcing](https://ctousman.hashnode.dev/microservices-event-pipelines-outbox-pattern-cdc?utm_source=hashnode&utm_medium=feed) Eliminate dual-write bugs in event-driven microservices with the Transactional Outbox Pattern, Debezium CDC, and idempotent Kafka consumers. 5 min read · [ctousman.hashnode.dev](https://ctousman.hashnode.dev/microservices-event-pipelines-outbox-pattern-cdc?utm_source=hashnode&utm_medium=feed) [Kgosi Leburu](https://hashnode.com/@kgosileburu) · [Sep 24](https://hashnode.com/posts/ehs-on-nokia-sr-os-why-event-driven-automation-needs-pysros/6ab4b857a146642fbed6cb79) ### [EHS on Nokia SR OS: Why Event-Driven Automation Needs pySROS](https://codednetwork.com/ehs-on-nokia-sr-os-why-event-driven-automation-needs-pysros?utm_source=hashnode&utm_medium=feed) Understanding the Event Handling System and how pySROS turns router events into automated action 7 min read · [codednetwork.com](https://codednetwork.com/ehs-on-nokia-sr-os-why-event-driven-automation-needs-pysros?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/ehs-on-nokia-sr-os-why-event-driven-automation-needs-pysros/6ab4b857a146642fbed6cb79) [Abhishek Banerjee](https://hashnode.com/@socialthinker) · [Sep 19](https://hashnode.com/posts/event-driven-architecture-in-2026-why-you-might-not-need-kafka/6aaec82f572c3c58f9d56687) ### [Event-Driven Architecture in 2026: Why You Might Not Need Kafka](https://deeper-in-tech.hashnode.dev/event-driven-architecture-in-2026-why-you-might-not-need-kafka?utm_source=hashnode&utm_medium=feed) Apache Kafka has long been the default choice for event streaming. Here is why lighter message brokers, modern bus topologies, and cloud-native queues often make more sense for 95% of asynchronous wor 5 min read · [deeper-in-tech.hashnode.dev](https://deeper-in-tech.hashnode.dev/event-driven-architecture-in-2026-why-you-might-not-need-kafka?utm_source=hashnode&utm_medium=feed) [Gowtham Behara](https://hashnode.com/@gbehara) · [Sep 18](https://hashnode.com/posts/event-driven-from-day-one-except-the-part-that-deliberately-wasn-t/6aadb697b31621352439f9fb) ### [Event-Driven From Day One (Except the Part That Deliberately Wasn't)](https://worksonmyproduction.hashnode.dev/event-driven-from-day-one-except-the-part-that-deliberately-wasn-t?utm_source=hashnode&utm_medium=feed) The one part of this system that isn't event-driven, on purpose. 9 min read · [worksonmyproduction.hashnode.dev](https://worksonmyproduction.hashnode.dev/event-driven-from-day-one-except-the-part-that-deliberately-wasn-t?utm_source=hashnode&utm_medium=feed) [Danny Crasto](https://hashnode.com/@danwald) · [Sep 16](https://hashnode.com/posts/design-a-notification-system/6aaad1bcc6793e20fd4fddeb) ### [Design a notification system](https://blog.danwald.me/design-a-notification-system?utm_source=hashnode&utm_medium=feed) There are three main types of notifications: push, email, and SMS. They are usually 'soft' real-time, and they should support opt-outs across multiple devices per user. Pushes are routed to Apple or F 2 min read · [blog.danwald.me](https://blog.danwald.me/design-a-notification-system?utm_source=hashnode&utm_medium=feed)