Java-Centric Web Development: The Advantages of a Single Stack Approach
summary
Argues that keeping frontend and backend in Java avoids cross-team friction and accidental complexity and shows a concrete tool, Web forj, used to rebuild a decade‑old US Health Insurance application that stalled with JavaScript contractors; a side‑by‑side comparison shows the Java single‑stack version has 60% fewer lines of application code and takes about 40% faster developer time (2.5–3 hours vs 4.5–5), with the customer reporting much faster progress after switching.
AI-written summary · about
chapters (16)
- 0:00Introduction and context
- 2:31Understanding the audience
- 4:41Agenda overview
- 6:30Challenges in modern development
- 8:22The cost of separation
- 9:30Addressing complexity
- 12:22The single stack alternative
- 14:02Streamlining team workflows
- 14:49Modernization decision paths
- 18:01Real-world success story
- 22:13Productivity analysis
- 23:40Code efficiency metrics
- 26:05Simple code examples
- 26:47Kotlin integration
- 27:25Advanced UI capabilities
- 28:31Conclusion and Q&A
related talks
49mThree Different Methods to Build Web UIs in Java
40mModernizing Java UIs Without JavaScript: Escape the Multi-Stack Trap
27m"Full-stack from the back: Building for the web with Java"
41mFull-stack development is dead, long live full-stack development!
42mReturn of the Full-Stack Developer
41mFull-Stack development is dead, long live Full-Stack development!
46mFull-stack Development is Dead, Long Live Full-stack Development!
51mReal World Lean Java Practices, Patterns, Hacks, and Workarounds