Location Transparency
summary
Argues that hiding component locations removes brittle dependencies so a monolith can split without changing business code, using Java message objects routed through Axon Framework and optionally Axon Server; implements command/event/query gateways that register handlers and route commands one-to-one, broadcast events, and return query results. Demonstrates you can deploy the same code locally or distributed with no API changes, at the cost of serialization and network overhead.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:59Coherence
- 7:00Kinescence
- 9:04Software
- 15:35Aggregate
- 16:34Coherent
- 17:04Kinescent
- 17:58Low Connections
- 24:13Location Awareness
- 25:51Commands
- 28:15Java Objects
- 29:24Message Router
- 36:25Outro
related talks
41mLocation transparency
52mBuilding monolith applications that could scale to microservices..
45mBuilding Monoliths that Could Scale (Easily) to Microservices (If They Need)
01h 12mDemystifying "event-based" software concepts and methodologies
45mThe Practical Road towards CQRS and Event Sourcing
37mHiding The Lead
50mEvent Driven Microservices with Axon and Spring Boot: excitingly boring
46mEvent-Driven Microservices - not (just) about Events!