Backend Development 5 min read

Getting Started with Quarkus: Creation, Development, and CI/CD Deployment

This article introduces the popular microservice stacks, explains Quarkus’s advantages, shows three ways to create a Quarkus project, demonstrates local development and port configuration, and provides a step‑by‑step Jenkins CI pipeline for building and running the application.

Practical DevOps Architecture
Practical DevOps Architecture
Practical DevOps Architecture
Getting Started with Quarkus: Creation, Development, and CI/CD Deployment

Common microservice technology stacks such as Spring Cloud, Spring Cloud Alibaba, Dubbo, and Spring Cloud Tencent are widely used, but they encounter integration issues with Docker and Kubernetes, leading to slow startup and high resource consumption.

Quarkus aims to surpass traditional Java stacks and offers several benefits: fast hot‑reload deployment, native image generation with GraalVM for 3‑12 ms startup (45‑70% performance gain), unified reactive and imperative programming, and built‑in extensions for libraries like Kafka and Hibernate.

There are three ways to create a Quarkus application:

1. Using Maven:

mvn io.quarkus.platform:quarkus-maven-plugin:2.16.5.Final:create \

-DprojectGroupId=org.acme \

-DprojectArtifactId=getting-started \

-Dextensions='resteasy-reactive'

2. Using IntelliJ IDEA (graphical steps omitted).

3. Using the official web builder at code.quarkus.io to select extensions and download a ready‑to‑import project.

After creating the project, you can start it in development mode with a single command:

mvn compile quarkus:dev

Quarkus supports JDK 11+ and runs on the default port 8080, which can be changed in application.properties (e.g., quarkus.http.port=9080 ).

For CI/CD, the article demonstrates pushing the code to a Git repository (GitLab example) and configuring a Jenkins job:

• Create a new Jenkins task and set the Git repository URL.

• Configure Maven settings in the job.

• Build the project; unlike traditional Maven builds, Quarkus uses an uber-jar packaging mode.

After a successful build, the generated JAR can be started on the target server with:

java -jar target/*-runner.jar

This workflow shows a complete pipeline from project creation to automated build and deployment of a Quarkus microservice.

JavamicroserviceskubernetesmavenQuarkusJenkins
Practical DevOps Architecture
Written by

Practical DevOps Architecture

Hands‑on DevOps operations using Docker, K8s, Jenkins, and Ansible—empowering ops professionals to grow together through sharing, discussion, knowledge consolidation, and continuous improvement.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.