adriens❔ About
I recently saw the following content popup:
We have adopted this technology in our Team at opt-nc and feel everyday a large amount of benefits on the DevEx and more generally on our whole DEVOPS pipeline.
After watching this content, I felt that sharing it internally may help improve our on-boarding process, so I decided to prepare a ready-to-use playlist on top of it.
🎯 What to expect
This post is dedicated to help people better understand where does Quarkus comes from and why it helps a lot... and why we love using it on our daily missions.
Each bookmark targets a specific aspect of this webinar so you can efficiently come and pick the point you must learn a bout within the next few minutes you have.
🪝 Focus points
Essentially, this playlist will cover the following aspects:
- 📜 Where does Quarkus come from: then & now
- 💳 Cloud concern and impact
- 📊 Application density (how much can be achieved with a given amount of resources)
- ℹ️ The cost of dynamism
- 🦥 DevEx : Testcontainers & devservices
- ⚖️ BUILD time vs. runtime considerations
- 🌿🌍 Green IT & carbon considerations
⚡ The MUST WATCH
Also, if you are very (very) short in time from my point of view, there are two MUST watch:
- 🔑 The cost of dynamism and core Quarkus concept
- ⚙️ Quarkus and the "closed world assummption: how does a framework start
📑 Playlist
- Intro
- Back in 2015
- 2022 : Fast & light runtimes
- 2011-2013 : Java shift to microservices, containers & cloud
- Container platform and is Java designed for the cloud: GO vs. javascript/node.js vs. Java
- Running application in the cloud concerns (start/stop often) bring apps up and down very often
- Applcation/service density and Quarkus
- KPIs Quarkus REST app startup time (Quarkus+graalVM, Quarkus +OPenJDK, )
- How does startup time matter (even without doing serverless) and auto-sclaing considerations
- Memory footprint and density considerations
- About throughput (native vs. JVM)
- MUST WATCH : the cost of dynamism and core Quarkus concept, immutable apps
- MUST WATCH : Quarkus and the "closed world assummption (and dev ex impact)" : BUILD time vs. runtime : pointless dynamic runtimes (about class loading, ) : how does a framework start
- (From scratch) Live code session (DevUI, database persistence w/ Panache, psql devcontainers, testcontainers, podman, service auto )
- testcontainers auto-provisioning and dev services (databases, redis, keycloak, kafka, elasticsearch, kubernetes, custom ones...) focus, configuration
- is Qharkus greener (KPIs, experiments, ) : Spoiler : native consumes more carbon than JVM
🔖 Additional resources
