Continuous Delivery with Docker Containers and Java EE
summary
Argues that packaging Java EE app server, app and deps in containers makes delivery faster, more predictable and less environment-crippled, shows Maven + Jenkins + Nexus + Docker workflows and a working demo of a centralized pipeline using Fabric8 on OpenShift origin that scaffolds git repos, Jenkins pipelines, image builds (S2I) and Kubernetes pods. Notes local Docker image builds take ~10 minutes, only ~6% of enterprises run Docker in production, and that the fabric8/OpenShift pipeline works but requires a beefy host and careful host/certificate setup. WildFly Swarm appears as a lightweight Java EE runtime option.
AI-written summary · about
chapters (6)
- 0:00Start
- 10:33TRADITIONAL SILOS
- 11:19BREAKING THEM DOWN (THE MICROSERVICE WAY)
- 11:57TRADITIONAL ARCHITECTURE
- 12:11TOMORROWS APPROACH (MICROSERVICES)
- 15:11PYRAMID OF MODERN APPLICATION DEVELOPMENT
related talks
01h 01mContinuous Delivery using Java EE 7
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
31mBuilding a private CI/CD pipeline with Java and Docker in the Cloud
49mContinuous Delivery at Docker age
41mRapid Application Development with Docker
45m12-Factor, Cloud Native Enterprise Java Applications
01h 00mRefactor your Java EE application using Microservices and Containers
32mDistroless Docker: Containerizing Apps, not VMs