Java EE - And The Bloat Is Gone
summary
Argues Java EE 6 removes the old XML and layer bloat so apps ship tiny WARs with no bundled jars and run on standard app servers; demos show 120k sessions on GlassFish with 500 MB RAM, recommends no external libraries unless absolutely needed, one domain per app and KVM per application for monitoring, and a compact build: Maven POM ~40 lines. Advocates concrete stack choices — EJB for transactions and CDI for DI — delete pointless interfaces, prototype in hours, and write unit tests for cyclomatic complexity >3.
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:15Java EE
- 6:36Project vs Product
- 9:00Start with coding
- 13:00No interfaces
- 15:20No external libraries
- 22:12No XML
- 24:13API
- 25:59Annotations
- 27:23Java Conferences
- 35:45Patterns
- 38:25Build
- 40:26Unit Tests
- 42:14No Reuse
related talks
10mpart1 – Adam Bien
01h 07mThe Java EE-stic Way of Coding
49mJava EEFuture Is Now, But It Is Not Evenly Distributed Yet
40m6 tips for your JavaEE project be less depressing
35mOptimize your applications to the max with Jakarta EE and MicroProfile
47mHow to Structure Jakarta EE Applications for Productivity Without Bloat
52mJava EE in Practice
56mModern Enterprise Java from the Ground Up