Skip to content

Commit cc30338

Browse files
committed
Clement's review
Signed-off-by: Michal Maléř <[email protected]>
1 parent 947315f commit cc30338

File tree

2 files changed

+17
-15
lines changed

2 files changed

+17
-15
lines changed

_posts/2025-10-23-mmaler-blogpost-2-quarkus-runtime-and-framework-for-cloud-native-java.adoc

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -14,30 +14,31 @@ ifdef::env-github,env-browser,env-vscode[:imagesdir: ../assets/images/posts/mmal
1414

1515
image::/assets/images/posts/mmaler-blog-posts/quarkus-as-a-powerful-runtime.jpeg[alt="Quarkus: Runtime and Framework for Cloud-Native Java", width=100%]
1616

17-
Cloud platforms reward services that start fast and stay lean.
18-
Quarkus is engineered for that reality: build-time processing reduces runtime overhead; the result is rapid startup, a small memory footprint, and frictionless deployment to containers, Kubernetes, and serverless.
19-
17+
Cloud platforms favor services that start fast and stay lean.
18+
Quarkus is engineered for exactly that.
19+
Build-time processing reduces runtime overhead and results in rapid startup, a small memory footprint, and frictionless deployment to containers, Kubernetes, and serverless.
2020
If your Java services need to start in milliseconds, run dense on shared nodes, and still feel great to build, Quarkus was made for that job.
2121

2222
Quarkus is a Java runtime that seamlessly integrates popular frameworks and libraries, shaping both the structure of modern applications and the developer experience behind them.
23-
2423
In this post, “runtime” means the full execution stack in production: JVM or native, plus Quarkus and the integrated frameworks.
2524

2625
Quarkus itself can also work as a framework, as it constitutes a higher-level layer that provides structure and APIs.
2726

28-
== Why Quarkus stands out
27+
== Why Quarkus stands out?
2928

3029
In modern software development, runtimes and frameworks form the foundation of productivity and consistency.
3130
Frameworks promote uniformity, simplify infrastructure, and enable automation at scale.
3231

3332
image::1-history.png[alt="A brief timeline leading to modern Java and Quarkus", width=100%]
3433

35-
Quarkus is a cloud-native Java runtime that integrates multiple frameworks and optimizes them for fast startup, low memory use, smooth Kubernetes/serverless deployments, and a great developer experience with live reload, which allows you to have very fast feedback by immediately seeing any changes you make to your code without the need to recompile and restart the server.
34+
Quarkus is a cloud-native Java runtime that integrates multiple frameworks and optimizes them for fast startup, low memory use, smooth Kubernetes and serverless deployments, and a great developer experience with live reload.
35+
Live reload provides fast feedback by showing code changes immediately without recompiling or restarting the server.
3636

37-
On top of that, Quarkus integrates established Java frameworks, such as CDI, JAX-RS, and Hibernate. However, it also enforces its own conventions, uses annotations to drive behavior, and defines how applications are structured.
37+
In addition to speed and live reload, Quarkus integrates established Java specifications such as CDI, JAX-RS, and JPA, with implementations provided by Arc (CDI), RESTEasy (JAX-RS), and Hibernate ORM (JPA).
38+
It also enforces its own conventions, drives behavior by using annotations, and defines how applications are structured.
3839

3940
In this sense, Quarkus is a framework that serves as a runtime and platform for cloud-native Java applications.
40-
It also adheres to industry standards, offering compatibility with technologies such as Spring, Kafka, and Camel to support familiar and flexible development models.
41+
It also adheres to industry standards, offering compatibility with technologies such as Spring, Apache Kafka, and Apache Camel to support familiar, flexible development models.
4142

4243
== Quarkus as a versatile framework
4344

@@ -129,24 +130,28 @@ Because Quarkus modularity is declarative and unified across extensions, it supp
129130

130131
=== Building your stack with Quarkus
131132

133+
We will explore this topic in depth in part three of this series.
134+
For now, here is how Quarkus fits into the picture.
135+
132136
Frameworks can serve as a foundation for creating higher-level abstractions.
133137

134138
Quarkus fits naturally into this model—not by becoming a platform itself, but by enabling teams to build their customized stacks and frameworks on top of it.
135139

136140
Unlike many traditional frameworks, Quarkus provides a unified extension architecture that supports deep customization.
137141
Organizations can tailor Quarkus to fit specific domains, technologies, or compliance needs.
138-
This enables the creation of organization-specific developer experiences, as seen in solutions like Amadeus’s SQube.
142+
This enables the creation of organization-specific developer experiences, including internal stacks built on a unified Quarkus extension architecture.
139143

140144
By encouraging consistency, offering build-time integration, and exposing clean extension points, Quarkus supports the creation of opinionated, scalable internal frameworks without forking or reinventing the core.
141145

142-
With Quarkus, teams can focus on business logic while the runtime handles infrastructure concerns, and the platform provides consistency across services.
143-
This has been exemplified by Logicdrop, who refactored their entire Spring Boot stack with Quarkus, reducing container size by ~75%, achieving sub-second startup times, and significantly improving developer productivity.
146+
By packaging Quarkus extensions, curated defaults, and service templates into an internal Quarkus stack, teams focus on business logic.
147+
At the same time, your framework layer standardizes infrastructure, security, and operational integrations across services.
148+
This has been exemplified by Logicdrop, which refactored its entire Spring Boot stack with Quarkus, reducing container size by ~75%, achieving sub-second startup times, and significantly improving developer productivity.
144149

145150
For more information, see the link:https://quarkus.io/blog/logicdrop-customer-story/[Logicdrop customer story] and their link:https://quarkus.io/blog/logicdrop-automating-quarkus-with-gitlab/?utm_source=chatgpt.com[GitLab automation write-up].
146151

147152
== Conclusion
148153

149-
Quarkus unifies the strengths of a framework and a runtime.
154+
Quarkus unifies the strengths of a development framework, and a runtime.
150155

151156
As a framework, it provides structure, conventions, and a cohesive developer experience. As a runtime, it delivers fast startup, low memory use, and operational consistency in the cloud.
152157

@@ -156,6 +161,3 @@ image::8-expectations.png[alt="Setting expectations for performance and develope
156161

157162
For a closer look at how Quarkus makes Java cloud-native, see the https://quarkus.io/blog/mmaler-blogpost-1-intro/[introductory blog post].
158163

159-
== What’s next?
160-
161-
Explore more Quarkus use cases in the link:https://quarkus.io/blog/[official blog archive], or check out the link:https://quarkus.io/guides/[Quarkus guides] to start building your own cloud-native stack today.
-38.2 KB
Loading

0 commit comments

Comments
 (0)