The Java EE-stic Way of Coding
summary
Advocates a pragmatic Java EE 7 workflow: start from a Maven archetype, write tiny WARs and REST endpoints, test them with a JAX‑RS client system test, and keep business logic in stateless EJBs/CDI so methods are fast and testable. Use managed executor services and configured thread pools as bulkheads (example: 5 threads, 5k requests) plus async/CompletableFuture to avoid blocking HTTP threads. Build Docker images by layering a base Java image and Payara, pushing small WARs (100–300MB) for fast deploys, and read server JSON (JSR‑77) for live metrics.
AI-written summary · about
chapters (11)
- 0:00Introduction and approach
- 2:20Project setup and philosophy
- 6:34Service architecture
- 10:33Testing strategies
- 15:01Design patterns and naming
- 18:52Resource management
- 21:44Java and Docker deployment
- 30:46Architectural principles
- 34:23Configuration and patterns
- 38:44Monitoring and performance
- 46:15Concurrency and robustness
related talks
49mJava EEFuture Is Now, But It Is Not Evenly Distributed Yet
44mJava EE - And The Bloat Is Gone
56mModern Enterprise Java from the Ground Up
49mRefactor Java EE application Microservices and Containers
47mHow to Structure Jakarta EE Applications for Productivity Without Bloat
51mReal World Lean Java Practices, Patterns, Hacks, and Workarounds
40m6 tips for your JavaEE project be less depressing
05mInterview