Real World (Enterprise) Java: Zero Bloat, Max Productivity
summary
Concrete claims and concrete tools: Java 21+ features enable a lean JDBC layer using Java records + sealed interfaces + pattern matching; prefer monoliths, use HTTP/JSON when distributed, and accept that JSON‑P/Jackson performance is “fast enough.” Cloud projects start with S3 as initial cloud storage and serverless Lambdas; avoid heavy frameworks and risky dependencies, favor MicroProfile/Quarkus on AWS. Built artifacts include reusable system‑test jars and a plugin loaded via service loader + java.util.Function — it works in production.
AI-written summary · about
chapters (14)
- 0:00Java in enterprise
- 4:16Java in cloud era
- 9:10Postmodern Java architecture
- 13:07BCE pattern explained
- 19:29Testing pitfalls and myths
- 23:02Java 21+ persistence
- 26:34Abstractions at project start
- 31:59Documentation and modularity
- 35:52Lombok debate
- 39:25Builds and deployments
- 42:14System tests strategies
- 43:37Feature branching challenges
- 45:42Overengineering and architecture clarity
- 47:28Data Access Objects and Transfer Objects reconsidered
related talks
51mProductivity, Sustainability, and Fun in modern Java
52mBulletproof Java Enterprise Applications for The Hard Production Life
50mModern Java microservices in the Cloud
45m12-Factor, Cloud Native Enterprise Java Applications
01h 02mJourney to Cloud : Leave No Java Workload Behind
58mEnhancing Java Applications for the Cloud
46mModern Enterprise Java from the ground up
59m5 tips to make your Java apps more awesome. Non-functional Requirements Exemplified
