|
1 | 1 | --- |
2 | 2 | layout: post |
3 | 3 | title: 'Quarkus as a Powerful Runtime' |
4 | | -date: 2025-10-21 |
5 | | -tags: quarkus runtime performance cloud-native |
| 4 | +date: 2025-10-23 |
| 5 | +tags: quarkus runtime framework performance cloud-native |
6 | 6 | synopsis: This post explores how Quarkus speeds up development, cuts costs, and makes development enjoyable for cloud-native Java. |
7 | 7 | author: mmaler |
8 | | -thumbnailimage: /assets/images/posts/mmaler-blog-posts/quarkus-as-a-powerful-runtime.png |
| 8 | +thumbnailimage: /assets/images/posts/mmaler-blog-posts/quarkus-as-a-powerful-runtime.jpeg |
9 | 9 | --- |
10 | | -:imagesdir: /assets/images/posts/mmaler-blog-posts/#2-Quarkus-as-a-powerful-runtime/ |
11 | | -ifdef::env-github,env-browser,env-vscode[:imagesdir: ../assets/images/posts/mmaler-blog-posts/#2-Quarkus-as-a-powerful-runtime/] |
| 10 | +:imagesdir: /assets/images/posts/mmaler-blog-posts/2-Quarkus-as-a-powerful-runtime/ |
| 11 | +ifdef::env-github,env-browser,env-vscode[:imagesdir: ../assets/images/posts/mmaler-blog-posts/2-Quarkus-as-a-powerful-runtime/] |
12 | 12 |
|
13 | | -= Quarkus as a powerful runtime |
| 13 | += Quarkus: Runtime and Framework for Cloud-Native Java |
| 14 | + |
| 15 | +In this post, “runtime” means the full execution stack in production: JVM or native, plus Quarkus and the integrated frameworks. |
14 | 16 |
|
15 | 17 | 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. |
16 | 18 |
|
| 19 | +From a complementary perspective, “framework” denotes the higher-level layer that provides structure and APIs; in this sense, Quarkus can also be viewed as a framework. |
| 20 | + |
17 | 21 | == Why Quarkus stands out |
18 | 22 |
|
19 | 23 | In modern software development, runtimes and frameworks form the foundation of productivity and consistency. |
@@ -118,11 +122,16 @@ This enables the creation of organization-specific developer experiences, as see |
118 | 122 |
|
119 | 123 | 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. |
120 | 124 |
|
121 | | -With Quarkus, teams can focus on business logic while the runtime handles infrastructure concerns, and the platform provides consistency across services. This is similar to 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. |
| 125 | +With Quarkus, teams can focus on business logic while the runtime handles infrastructure concerns, and the platform provides consistency across services. |
| 126 | +This is similar to 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. |
122 | 127 |
|
123 | 128 | == Conclusion |
124 | 129 |
|
125 | | -Runtimes that act as platforms offer scale, safety, and speed. Quarkus delivers all three, with the performance Java needs in the cloud and the developer joy it deserves. |
| 130 | +Quarkus unifies the strengths of a framework and a runtime. |
| 131 | + |
| 132 | +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. |
| 133 | + |
| 134 | +This dual role helps teams standardize practices, reduce costs, and ship resilient cloud-native services with confidence and the developer joy it deserves. |
126 | 135 |
|
127 | 136 | image::8-expectations.png[scaledwidth=100%] |
128 | 137 |
|
|
0 commit comments