Embracing Change (...)
summary
Company migrates a small microservice to Clojure on JVM while keeping Java EE elsewhere, drops heavyweight app servers for slimmer Docker images, and adds a simple health-check endpoint that proves production liveness. Builds a Gradle wrapper around Clojure tooling to fit existing CI, reuses JVM monitoring and metrics, and avoids rewriting complex Java EE integrations by implementing tiny adapters or leaving them in Java. The first Clojure service deploys successfully and its health check works.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:52Java EE to microservices
- 1:59Java EE challenges
- 3:25Discovering Clojure
- 4:31Overcoming skepticism
- 5:43Cross-team collaboration
- 7:08Simplifying Clojure setup
- 8:37Gradle plugin issues
- 9:48Small targets for adoption
- 11:30Client trust and production
- 12:57Monitoring in Clojure
- 14:03Java interoperability
- 15:06Key takeaways
related talks
50mOperating Clojure Microservices
53mMicroservices on Java EE — As Cool As The LHC
42mCloud Native Java EE
30mGrowing Clojure Systems. From Functions to Microservices
01h 00mRefactor your Java EE application using Microservices and Containers
45m12-Factor, Cloud Native Enterprise Java Applications
56mModern Java microservices in the Cloud!
59mJava microservices from Netflix OSS to Kubernetes
