Quarkus
Introduction to Quarkus
- Quarkus was created to enable Java developers to create applications for a modern, cloud-native world.
- Quarkus is a Kubernetes-native Java framework tailored for GraalVM and Hotspot, crafted from best-of-breed Java libraries and standards.
- The goal is to make Java the leading platform in Kubernetes and serverless environments while offering developers a framework to address a wider range of distributed application architectures.
- It is Supersonic and Subatomic. Here Supersonic means that the jar files of Quarkus are very fast executable and Subatomic means that the jar files are very small in Quarkus as compared to other frameworks.
- In simple, less memory and faster loading time.
- In Quarkus only those class files gets executed which are needed.
Why Quarkus ?
First question that arises in our mind is that why should we use Quarkus over other framework like Springboot.
Reason:
- Quarkus works on ahead of time compilation strategy, what it does is it will compile your code in background before we build our application.
- All the processing is done in build time, so our application will contain only those classes which are actually needed during runtime.
- In the traditional model like other framework all the classes required to perform the initial application deployment & it hangs around till the life of the application, but with Quarkus it’s not the case.
- It also unifies the imperative and reactive approach of development. So that we can use any of the style during the development.
Benefits of Quarkus
In simple word Quarkus is the cohesive platform for the developer joy:
- Unified configuration
- Zero config, live reload in the blink of eye. Quarkus basically did not end the JVM process and start it again like other frameworks, it simply end the Quarkus and restart it & do the work with a supersonic speed.
- Streamline code for the 80% common usages, flexible for the 20%.
- No hassle native executable generation.
With all this, let’s end this blog as this is it of Quarkus Basics. If you will find any issue regarding concept or code, you can message me on my Twitter or LinkedIn. The next blog will be published on 28/02/23.
Some words about me
I’m Mohit.❤️ You can also call me Chessman. I’m a Machine learning Developer and a competitive programmer. Most of my time is spent staring at a computer screen. During the day, I am usually programming, working to derive insight from large datasets. My skills include Data Analysis, Data Visualization, Machine learning, Deep Learning, DevOps and working toward Full Stack. I have developed a strong acumen for problem-solving, and I enjoy occasional challenges.
