Location transparency
summary
Defines location transparency as hiding where handlers live by exchanging typed messages and shows a concrete router that treats commands, events, and queries differently: commands route to a single handler with confirmation, events are fire‑and‑forget and append to an event store with near‑linear write performance, queries return results and can aggregate responses. Demonstrates registering handlers, gateways for sending messages, and the ability to run identical components either inside one process or distributed without changing their code.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:42My house
- 4:09Coherence
- 5:47Coupling
- 6:50knessencekinesis
- 7:36ticket
- 8:06connections of name
- 9:35connections of algorithm
- 10:52types of connections
- 11:59Aggregate
- 14:06Connections
- 15:29Explanation
- 19:39Message types
- 21:33Message model
- 22:04Message router
- 23:09Example code
- 25:01Accent framework
- 26:38Single deployment unit
- 30:06Summary
- 30:38Questions
- 32:27Performance
related talks
44mLocation transparency (for Java developers)
38mLocation Transparency
55mLocation transparency (for Java developers)
52mModern Observability and Event Driven Architectures
53mMessaging: The fine line between awesome and awful
03mTurning Request-response on its Head
54mDemystifying ‘Event’ Related Software Concepts and Methodologies
35mBuilding Scalable Stateful Services