Apply suggestions from code review

Co-authored-by: Jiri Herrmann <[email protected]>

Author: MichalMaler

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

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: 'Quarkus: Runtime and Framework for Cloud-Native Java'
+title: 'Quarkus: A Runtime and Framework for Cloud-Native Java'
 date: 2025-10-22
 tags: quarkus runtime framework performance cloud-native
 synopsis: This post explores how Quarkus speeds up development, cuts costs, and makes development enjoyable for cloud-native Java.
@@ -10,14 +10,14 @@ thumbnailimage: /assets/images/posts/mmaler-blog-posts/quarkus-as-a-powerful-run
 :imagesdir: /assets/images/posts/mmaler-blog-posts/2-Quarkus-as-a-powerful-runtime/
 ifdef::env-github,env-browser,env-vscode[:imagesdir: ../assets/images/posts/mmaler-blog-posts/2-Quarkus-as-a-powerful-runtime/]
 
-= Quarkus: Runtime and Framework for Cloud-Native Java
+= Quarkus: A Runtime and Framework for Cloud-Native Java
 
 image::/assets/images/posts/mmaler-blog-posts/quarkus-as-a-powerful-runtime.jpeg[alt="Quarkus: Runtime and Framework for Cloud-Native Java", width=100%]
 
 In this post, “runtime” means the full execution stack in production: JVM or native, plus Quarkus and the integrated frameworks.
 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.
 
-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.
+Quarkus itself can also work as a framework, as it constitutes a higher-level layer that provides structure and APIs.
 
 == Why Quarkus stands out
 
@@ -35,7 +35,7 @@ In this sense, Quarkus is a framework that serves as a runtime and platform for
 
 == Quarkus as a versatile framework
 
-Beyond standard traits common to modern frameworks, Quarkus introduces two platform-defining features: build-time optimization and deep extensibility.
+Beyond staple traits of modern frameworks, Quarkus introduces two platform-defining features: build-time optimization and deep extensibility.
 
 * *Build-time optimization*: Quarkus shifts work from runtime to build time wherever possible.
 This approach reduces startup overhead and memory usage, resulting in a lean, fast, and efficient application tailored for production.
@@ -50,7 +50,7 @@ image::5-JVM-Snapshotting-Native.png[alt="JVM snapshotting vs native images in Q
 
 * *Extensibility*: Quarkus exposes extension points for everything from startup hooks to request filters.
 Over 800 extensions allow seamless integration with modern technologies such as Kafka, OpenTelemetry, and OpenID Connect.
-
++
 These extensions integrate with Quarkus and participate in its build-time and runtime lifecycle, making them first-class citizens of the Quarkus platform.
 
 === Simplified developer experience
@@ -76,14 +76,14 @@ As discussed in the link:https://cacm.acm.org/practice/application-frameworks/[A
 
 Native image generation with GraalVM enables cold starts in milliseconds and a minimal memory footprint, allowing cost-effective deployment in containers and serverless environments.
 
-Quarkus also includes structured health checks, metrics, and tracing, thereby aligning with production standards from day one.
+Quarkus also includes structured health checks, metrics, and tracing, and thereby aligns with production standards from day one.
 
 image::7-success-stories.png[alt="Real-world success stories using Quarkus", width=100%]
 
 
 === Security
 
-Quarkus uses a standards-first, composable, security model.
+Quarkus uses a standards-first composable security model.
 You enable what you need and configure it for your environment:
 
 * **Transport:** Enable TLS for HTTPS, or terminate TLS at your ingress.
@@ -94,7 +94,7 @@ This lets you apply the right security controls for each deployment.
 
 === Observability and control surfaces
 
-Common control surfaces, such as metrics, logging, tracing, and configuration, are essential for Site Reliability Engineers (SREs) and platform teams.
+Common control surfaces, such as metrics, logging, tracing, and configuration, are essential for site reliability engineers (SREs) and platform teams.
 
 Quarkus exposes:
 
@@ -112,7 +112,7 @@ Following a lean-core, modular-at-the-edge approach, Quarkus delivers:
 * Pluggable modules for authentication, tracing, messaging, and more.
 * Dev Services for automatic provisioning of databases, brokers, and containers in dev mode.
 
-Whether you're building a prototype or deploying to OpenShift, Quarkus adapts.
+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.
 
 Because Quarkus modularity is declarative and unified across extensions, it supports a platform-like developer experience without the rigidity of traditional frameworks.
@@ -130,17 +130,17 @@ This enables the creation of organization-specific developer experiences, as see
 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.
 
 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.
+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.
 
 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].
 
 == Conclusion
 
 Quarkus unifies the strengths of a framework and a runtime.
 
-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.
+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.
 
-This dual role helps teams standardize practices, reduce costs, and ship resilient cloud-native services — while preserving developer joy.
+This dual role helps teams standardize practices, reduce costs, and ship resilient cloud-native services.
 
 image::8-expectations.png[alt="Setting expectations for performance and developer experience with Quarkus", width=100%]