ENTERPRISE J2EE
A production-style enterprise application — scalable typed APIs, an Angular front-end, and fully containerized deployment infrastructure.
ORGANIZATION
ACADEMIC BUILD — ESTEM CASABLANCA
PERIOD
2025 — 2026
ROLE
FULL STACK — SOLO
STACK
JAVA J2EE · ANGULAR · DOCKER
01 — THE BRIEF
Most coursework proves you can make something run once, on one machine. This build set a higher bar: an enterprise application assembled the way industry actually ships them.
Typed Java J2EE APIs, an Angular front-end consuming them, and the whole system containerized with Docker — production patterns practiced deliberately, not discovered by accident on the first job.
02 — OPERATING CONSTRAINTS
- Enterprise discipline as the goal: typed contracts, layered architecture, deployable infrastructure.
- The Java J2EE + Oracle stack of large institutions — chosen for realism, not comfort.
- Everything reproducible: if it only runs on the dev machine, it doesn't count.
03 — SYSTEM STRUCTURE
ANGULAR FRONT-END
A typed SPA consuming the API contract.
JAVA J2EE — TYPED APIS
Scalable, contract-first services in the pattern large institutions run on.
DOCKER — CONTAINERIZED DEPLOYMENT
The full system packaged and reproducible on any machine — infrastructure as part of the build.
04 — KEY DECISIONS
DECISION 01
Typed contracts on both sides
Java's typed APIs and Angular's typed client catch integration drift at compile time — the discipline enterprise teams depend on.
DECISION 02
Containerize from day one
Deployment treated as part of the application, not an afterthought — the system ships as infrastructure, not instructions.
DECISION 03
Practice the heavyweight stack deliberately
J2EE runs banks, insurers, and government systems. Fluency in it widens the range of environments he can drop into.
05 — OUTCOME
A production-style enterprise app with deployable infrastructure — industry patterns, proven before industry demands them.
- · Complements the Django/DRF enterprise work at Capgemini — two enterprise stacks, one engineer.
CROSS-EXAMINATION
The full walkthrough — code, schema, trade-offs — happens live. Fifteen minutes, no slides.
NEXT EXHIBIT
AMOS →