You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2025-11-14-mmaler-blogpost-2-quarkus-runtime-and-framework-for-cloud-native-java.adoc
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,8 @@ Quarkus does exactly that:
72
72
* Preconfigures popular libraries with sensible defaults.
73
73
* Offers unified configuration and developer tooling.
74
74
* Provides instant feedback with live reload and continuous testing.
75
+
* Dev Services for automatic provisioning of databases, brokers, and other services in dev mode.
76
+
* Continuous testing to run tests in the background and surface results immediately.
75
77
76
78
This makes Quarkus both powerful and approachable.
77
79
@@ -132,7 +134,8 @@ Common control surfaces, such as metrics, logging, tracing, and configuration, a
132
134
Quarkus exposes:
133
135
134
136
* Unified logging with link:https://quarkus.io/guides/logging[`quarkus-logging`].
135
-
* Structured metrics and tracing with link:https://quarkus.io/guides/telemetry-micrometer-to-opentelemetry[Micrometer and OpenTelemetry].
137
+
* Centralized logging with OpenTelemetry (OTLP logs) with link:https://quarkus.io/guides/opentelemetry[OpenTelemetry].
138
+
* Metrics and tracing with link:https://quarkus.io/guides/telemetry-micrometer-to-opentelemetry[Micrometer and OpenTelemetry].
136
139
* Unified configuration of all the application's aspects by using `application.properties` or environment variables.
137
140
138
141
This standardization enables automation and scalable monitoring.
@@ -143,7 +146,8 @@ Following a lean-core, modular-at-the-edge approach, Quarkus delivers:
143
146
144
147
* A minimal core for fast startup.
145
148
* Pluggable extensions for authentication, tracing, messaging, and more.
146
-
* Dev Services for automatic provisioning of databases, brokers, and containers in dev mode.
149
+
* Built-in production primitives, including health checks, readiness and liveness probes, and graceful shutdown.
150
+
* Fault tolerance with standard annotations, for example, retries, circuit breakers, bulkheads, and timeouts.
147
151
148
152
Whether you are building a prototype or deploying to OpenShift, Quarkus adapts.
149
153
This modularity spans both the framework-level APIs developers work with and the runtime behaviors that execute beneath them.
@@ -157,7 +161,7 @@ For now, here is how Quarkus fits into the picture.
157
161
158
162
Frameworks can serve as a foundation for creating higher-level abstractions.
159
163
160
-
Quarkus fits naturally into this model — not by becoming a platform in itself, but by enabling teams to build their customized stacks and frameworks on top of it.
164
+
Quarkus fits this model by enabling teams to build customized stacks and internal frameworks on top of it.
161
165
162
166
Unlike many traditional frameworks, Quarkus provides a unified extension architecture that supports deep customization.
163
167
Organizations can tailor Quarkus to fit specific domains, technologies, or compliance needs.
0 commit comments