Event-Driven Microservices logopeterindia.net
Knowledge Hub

Event-Driven Microservices: Guides, Tutorials & Resources

A curated list of guides, tutorials and references on building microservices that communicate through events — architecture overviews, best practices, hands-on tutorials and a sample project.

32 topics•5 categories•Updated October 2026

Architecture Overviews

7 entries

What event-driven microservices are and when to use them.

01Event-Driven MicroservicesEvent-Driven Microservices — enabling pub/sub communication at scale 02Event Driven Architecture and its MicroservicesEvent Driven Architecture and its Microservices — a comprehensive guide 03Embracing Event-Driven Microservices ArchitecturesEmbracing Event-Driven Microservices Architectures 04Architectural considerations for event-driven microservices-based systemsArchitectural considerations for event-driven microservices-based systems 05Microservices Architectures - Event Driven ApproachMicroservices Architectures — Event Driven Approach 06From Monolithic Architecture to Microservices and Event-Driven SystemsFrom Monolithic Architecture to Microservices and Event-Driven Systems 07Confluent: Event-Driven ArchitectureConfluent's guide to event-driven architecture and event-first thinking.

Best Practices & Patterns

6 entries

Design guidance and data-consistency patterns.

08Best Practices for Event-Driven Microservice ArchitectureBest Practices for Event-Driven Microservice Architecture 09Event-Driven Microservice ArchitectureEvent-Driven Microservice Architecture — the outbox pattern in practice 10Event-Driven Data Management for MicroservicesEvent-Driven Data Management for Microservices 11Building event driven microservices that scalesBuilding Event Driven Microservices That Scale 12Event Sourcing (microservices.io)Pattern for storing state as a sequence of events. 13Transactional Outbox (microservices.io)Pattern for reliably publishing events with database changes.

Tutorials with Kafka, Spring & Azure

4 entries

Hands-on guides for specific stacks.

14Building Simple Event Driven Microservices with Spring Cloud StreamBuilding Simple Event Driven Microservices with Spring Cloud Stream 15Microservices, Event-Driven Architecture and KafkaMicroservices, Event-Driven Architecture and Kafka 16Event-driven microservices with Apache KafkaEvent-Driven Microservices with Apache Kafka 17Event Driven Microservices with Azure Functions, Event Grid and Cosmos DBEvent Driven Microservices with Azure Functions, Event Grid and Cosmos DB

Book & Sample Code

2 entries

Deeper reading and working code.

18Building Event-Driven Microservices (Book)Building Event-Driven Microservices — Chapter 1: Why Event-Driven Microservices 19Event-Driven Microservices Backend Sample (GitHub)Event-Driven Microservices Backend Sample — Docker & RabbitMQ reference implementation. The GitHub repository's last commit was in August 2020, so check its activity before relying on it.

Related Pages

13 entries

Related directories on this site.

20Event-driven ArchitectureEvent-driven architecture hub. 21EDA Design PatternsEvent sourcing, CQRS, saga and messaging patterns. 22Microservices ArchitectureMicroservices architecture hub. 23Event Brokering SoftwareBrokers and event streaming. 24Apache KafkaKafka and the streaming ecosystem. 25Legacy Application ModernizationModernizing legacy applications. 26Streaming DatabasesDatabases that keep SQL results continuously up to date over event streams. 27Streaming Analytics PlatformsPlatforms for analysing event streams as they arrive. 28Event MeshesEvent mesh solutions that route events across clouds and sites. 29EDA ResourcesGuides, whitepapers and standards for event-driven architecture. 30Message Queue SoftwareRabbitMQ, ActiveMQ, IBM MQ, SQS, NATS and task queues. 31Publish/Subscribe (Pub/Sub) MessagingCloud pub/sub, brokers, MQTT and real-time messaging. 32Stream Processing FrameworksFlink, Kafka Streams, Spark, ksqlDB and streaming databases.

Frequently Asked Questions

What are event-driven microservices?

Microservices that communicate by publishing and reacting to events through a broker, rather than calling each other directly, which decouples services and supports asynchronous scaling.

Why use events between services?

They reduce coupling, absorb load spikes, support multiple consumers of the same data and make auditing and replay possible.

What are the main challenges?

Eventual consistency, ordering and duplicate delivery, schema evolution and debugging across services; patterns such as the outbox and sagas address several of these.

Which broker should I start with?

Apache Kafka is the most common choice for streaming; see the Event Brokering Software page for alternatives.

How does this support modernization?

Events let you carve services out of a monolith gradually and integrate legacy systems without tight coupling.

Which links may need a manual click?

Links were rechecked in October 2026. DZone, a Trendyol Medium article and the O'Reilly book page returned 403 to automated checks and are kept; they may need a manual click. For related directories, see Microservices Architecture, Event-Driven Microservices, Service Meshes and EDA Resources on this site.