Applying feedback from Bruno Baptista's review

Signed-off-by: Michal Maléř <[email protected]>

Author: MichalMaler

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

@@ -40,7 +40,7 @@ This shortens the inner loop and helps teams iterate faster than traditional red
 But beyond speed and live reload, Quarkus integrates established Java specifications such as CDI-Lite, JAX-RS, and JPA, with implementations provided by Arc (CDI-Lite), RESTEasy (JAX-RS), and Hibernate ORM (JPA).
 It also enforces its own conventions, drives behavior with annotations, and defines how applications are structured.
 
-In this sense, Quarkus is a framework that also serves as a runtime and platform for cloud-native Java applications.
+In this sense, Quarkus is a development framework and runtime for cloud-native Java applications.
 It adheres to industry standards and offers compatibility with technologies such as Spring, Apache Kafka, and Apache Camel to support familiar, flexible development models.
 
 == Quarkus as a versatile framework
@@ -62,7 +62,7 @@ image::4-BuildTimeP-Benefits-native.png[alt="Benefits of Quarkus native image co
 * *Extensibility*: Quarkus exposes extension points for everything from startup hooks to request filters.
 Over 800 link:https://extensions.quarkus.io[extensions] allow seamless integration with modern technologies such as Kafka, OpenTelemetry, and OpenID Connect.
 +
-These extensions integrate with Quarkus and participate in its buildtime and runtime lifecycle, making them first-class citizens of the Quarkus platform.
+These extensions integrate with Quarkus and participate in its buildtime and runtime lifecycle, making them first-class components of Quarkus.
 
 === Simplified developer experience
 
@@ -72,6 +72,8 @@ Quarkus does exactly that:
 * Preconfigures popular libraries with sensible defaults.
 * Offers unified configuration and developer tooling.
 * Provides instant feedback with live reload and continuous testing.
+* Dev Services for automatic provisioning of databases, brokers, and other services in dev mode.
+* Continuous testing to run tests in the background and surface results immediately.
 
 This makes Quarkus both powerful and approachable.
 
@@ -88,8 +90,9 @@ Teams optimize for different goals, such as startup latency, sustained throughpu
 Quarkus addresses these needs by shifting work from run time to build time, keeping one development model across JVM and native, and exposing production signals such as health checks, metrics, and tracing.
 
 Start with **JVM mode** for most services.
-It starts slower and uses more memory than native to start with, but just-in-time compilation raises steady-state throughput, scales well across cores, and offers mature garbage collectors and tuning options.
-Quarkus can often start faster on the JVM than typical Spring Boot setups under comparable conditions because more work happens at build time.
+On the JVM, Quarkus often starts faster and uses less memory than traditional JVM-based runtimes because it performs more work at build time.
+Just-in-time compilation raises steady-state throughput, scales well across cores, and offers mature garbage collectors and tuning options.
+The JVM also provides rich observability and diagnostics, which help you understand and tune live systems.
 
 Use **native mode** when startup latency and memory footprint are strict constraints.
 Native executables start in milliseconds and can use less memory, which supports scale-to-zero workflows and lowers idle costs on small instances.
@@ -132,7 +135,8 @@ Common control surfaces, such as metrics, logging, tracing, and configuration, a
 Quarkus exposes:
 
 * Unified logging with link:https://quarkus.io/guides/logging[`quarkus-logging`].
-* Structured metrics and tracing with link:https://quarkus.io/guides/telemetry-micrometer-to-opentelemetry[Micrometer and OpenTelemetry].
+* Centralized logging with OpenTelemetry (OTLP logs) with link:https://quarkus.io/guides/opentelemetry[OpenTelemetry].
+* Metrics and tracing with link:https://quarkus.io/guides/telemetry-micrometer-to-opentelemetry[Micrometer and OpenTelemetry].
 * Unified configuration of all the application's aspects by using `application.properties` or environment variables.
 
 This standardization enables automation and scalable monitoring.
@@ -143,7 +147,8 @@ Following a lean-core, modular-at-the-edge approach, Quarkus delivers:
 
 * A minimal core for fast startup.
 * Pluggable extensions for authentication, tracing, messaging, and more.
-* Dev Services for automatic provisioning of databases, brokers, and containers in dev mode.
+* Built-in production primitives, including health checks, readiness and liveness probes, and graceful shutdown.
+* Fault tolerance with standard annotations, for example, retries, circuit breakers, bulkheads, and timeouts.
 
 Whether you are building a prototype or deploying to OpenShift, Quarkus adapts.
 This modularity spans both the framework-level APIs developers work with and the runtime behaviors that execute beneath them.
@@ -157,7 +162,7 @@ For now, here is how Quarkus fits into the picture.
 
 Frameworks can serve as a foundation for creating higher-level abstractions.
 
-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.
+Quarkus fits this model by enabling teams to build customized stacks and internal frameworks on top of it.
 
 Unlike many traditional frameworks, Quarkus provides a unified extension architecture that supports deep customization.
 Organizations can tailor Quarkus to fit specific domains, technologies, or compliance needs.