The Crucial Role of Openness in Modern Software Development
summary
Argues that openness—concrete use of Jakarta EE and MicroProfile—delivers measurable benefits: standardized security practices and container-based configs cut misconfig time, modular MicroProfile plus Kubernetes and Docker integration shrinks service size and speeds cloud moves, built-in metrics/tracing/health checks enable safer experiments, and Jakarta’s backward compatibility keeps legacy systems running while modernizing. Recommends early adoption and active contribution to projects; community-driven specs and vendor partnerships are the mechanism that make these outcomes achievable.
AI-written summary · about
chapters (8)
- 0:00Introduction to openness
- 0:44Key components of openness
- 3:30Jakarta EE and MicroProfile
- 4:35Open Standards benefits
- 7:46Longevity and compatibility
- 9:55Accessibility and adaptability
- 11:40Adopting Open Standards
- 13:47Q&A on Java contributions
related talks
52mA Freakonomic Take on Open Standards and Jakarta EE
01mA Freakonomic Take on Open Standards and Jakarta EE
35mMicroProfile and Jakarta EE -- What's Next?
34mJakarta EE: The Future of Cloud Native Java is Open!
07mThe evolution of open source in enterprise environments
42mOpen Source in the Age of Cloud and Microservices
58mBuilding Enterprise Software Today: A partnership in openness
48mCloud Native Java at the Eclipse Foundation - Not your parent's Eclipse!