part1 – Adam Bien

on YouTube ↗10m

" summary

Productive Java EE 6 Rethinking Best Practices shows pragmatic outcomes: an enterprise app where about deleted ~80% of layers simplifies changes to one UI tweak instead of cascading edits, vendor switches occur with no code changes, XML configuration disappears, and transactional persistence returns identical references instead of many duplicates. Measured costs are small — EJB3 overhead ~3% (~1 ms) — and the EJB container on GlassFish is tiny — GlassFish EJB container ~400KB so lean deployments actually work.

AI-written summary · about

" related talks

• 44mJava EE - And The Bloat Is GoneAdam Bien · infoShare 2013
• 43mWho's afraid of the EJB?Alex Theedom · JavaDay Ukraine 2017
• 49mJava EEFuture Is Now, But It Is Not Evenly Distributed YetAdam Bien · JDD 2012
• 52mJava EE in PracticeLars Bilger, Ivo Kammerath · JavaOne 2015
• 47mHow to Structure Jakarta EE Applications for Productivity Without BloatAdam Bien · Oracle Code One 2018
• 40m6 tips for your JavaEE project be less depressingJakub Marchwicki · JDD 2016
• 01h 07mThe Java EE-stic Way of CodingAdam Bien · Jfokus 2016
• 05mJavaOne Shanghai: Bert ErtmanBert Ertman · JavaOne Shanghai 2013