Understanding Quarkus: Rethinking Java for Cloud-Native Applications

Here is my naive attempt at explaining Quarkus and its ecosystem. In the previous post , we discussed what caused the need of a different approach to java web applications. Before we begin, I want to clarify, that by no means, I mean to impose Quarkus' preference over Spring Boot. Infact, I get amazed by Spring internals, their design philosophy and seamless developer experience. Spring remains the primary choice for various usecases. One such example is Monoliths and long-running services where initial startup time is less critical than sustained high throughput and stability over extended periods. Also, Spring remains a developer's top choice, owning to convenience and large ecosystem while Quarkus ecosystem is small but growing. Now let's comeback to the topic. Here, you will be introduced to CDI. CDI stands for Contexts and Dependency Injection . It is a standard Jakarta EE (formerly Java EE) specification that simplifies the development of complex applications and ensures object l