Explore pragmatic approaches to event-driven microservices architecture in this conference talk from GOTO Amsterdam 2018. Dive into key concepts such as Command Query Responsibility Segregation (CQRS), event sourcing, and the differences between microservices and monoliths. Learn about effective messaging strategies, including command routing, query subscriptions, and event store operations. Discover how to balance sharing within contexts while consciously managing interactions between them. Gain insights on implementing "just enough" intelligence in microservices messaging to create robust, scalable systems. Perfect for developers and architects looking to enhance their understanding of event-driven design in modern software architecture.
Overview
Syllabus
Intro
Layered architecture
Command Query Responsibility Segregation
Microservices vs Monoliths
Noun Driven Design
Location transparency
Event-Driven' Microservices
Reasons to send a message
Competing consumers
Balanced consumers
I want something done - Command
Command Routing
I want to know something - Query
Query – subscription
Event Sourcing
Event Store operations
Unmanageable mess
Within a context, share everything
Between contexts, share 'consciously
Microservices Messaging
"Just enough" intelligence
Taught by
GOTO Conferences
Related Courses
-
Node.js Microservices: Advanced Topics and Best Practices
-
Microservices, Events, and Docker: A Perfect Trio for Agile Development
-
Kubernetes and Microservices with Oracle Database
-
Event Sourcing and Event Storage with Apache Kafka - Event Sourcing 101
-
Developing Event-Driven Microservices with Event Sourcing and CQRS - Philly ETE 2015
-
Event-Sourcing Your React-Flux Applications
