Location transparency (for Java developers)
summary
Argues that replacing direct calls with typed messages and a router yields practical location transparency: model commands, events and queries as POJOs, send via gateways, handle by annotated handlers, and you remove location coupling while keeping name/type coupling only. Describes a working implementation: axon framework for in‑JVM routing and axon server (free standard edition) as a distributed router that uses gRPC, plus an HTTP bridge, so a component can be moved to another machine without changing application code.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:56House analogy vs microservices
- 7:48Coherence vs coupling explained
- 10:19Connaissance in software
- 16:40Designing evolvable systems
- 20:52Location awareness problem
- 26:24Message types and intent
- 32:04Building location transparent system
- 35:57Framework for location transparency
- 38:26Distributed deployment options
- 42:03Key takeaways and Q&A
related talks
55mLocation transparency (for Java developers)
41mLocation transparency
01h 12mDemystifying "event-based" software concepts and methodologies
01h 00mFantastic Frameworks and How to Avoid Them
46mAxon Framework : A CQRS Approach to Microservices
51mA Clean, Pragmatic Architecture
41mJava Beyond Frameworks: Avoiding Lock-In with Agnostic Design
39mRethinking Line of Business Applications: Graphs & Cypher as an Alternative to RDBMS & SQL