Microservices running natively on ARM devices
summary
Quarkus native apps claim ~90% lower startup and runtime resource use and the demo runs a native ARMv8 containerized microservice on a Raspberry Pi 3/4 that cold-starts in 75 ms on Raspberry Pi 3 B+. Build uses multi-arch tooling with QEMU emulation to cross-compile on x86 and pushes images to registries; runtime uses Podman/podman-compose on the device and single-node OpenShift at the edge. Architecture adds Kafka/AMQ streams, MongoDB, InfluxDB and cert-manager + HashiCorp Vault for distributed certificate issuance and renewal.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:59Self introduction
- 3:28Technical
- 4:55Business
- 7:04Overall architecture
- 8:18Edge Device architecture
- 8:52Edge Server architecture
- 9:55Datacenter architecture
- 21:18What about my development workflow?
related talks
30mBattle Of The Microservice Frameworks: Micronaut versus Quarkus edition!
47mJava App Development in the Cloud: MicroProfile, Quarkus and Cloud.
53mMeet Quarkus
42mKeynote: Subatomic Java Microservices with Quarkus
45mFaster, greener, and happier- why Quarkus should be your next tech stack
43mQuarkus Native - from Scratch to Production
51mModern Java App Development in the Cloud
36mPragmatic App Migration to the Cloud: Quarkus, Kotlin, Hazelcast, GraalVM in action