Location transparency (for Java developers)
summary
Explains how Java developers can use location transparency to reduce tight coupling and connascence when breaking a monolith into distributed microservices, showing which method/class/package/module dependencies hinder decomposition. Demonstrates where to apply location transparency in code and discusses how it supports architectural patterns—Domain-Driven Design, CQRS, and Event Sourcing—to manage complexity during independent deployment and system growth.
AI-written summary · about
related talks
44mLocation transparency (for Java developers)
41mLocation transparency
59mDecomposing Java applications
49mMid-sized building blocks and hexagonal architecture
51mHiding The Lead: Coupling, Cohesion, and Microservices-Style
01h 01mModels, Modules, Microservices – Better Domain Models with Java 9 Modules
50mDecomposing Java applications
33mFrom Enterprise Architecture to Software Design - Critical Thinking