#quarkus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #quarkus, aggregated by home.social.
-
A timed-out POST can still commit. Retrying it may create a second order, payment, or fulfillment request.
I built a Quarkus checkout demo around the HTTP Idempotency extension and tested the full state machine: first request, stored replay, concurrent 409, payload mismatch, and missing keys. The production section also covers the Redis 0.1.0 blocker and the crash window around external side effects.
-
A timed-out POST can still commit. Retrying it may create a second order, payment, or fulfillment request.
I built a Quarkus checkout demo around the HTTP Idempotency extension and tested the full state machine: first request, stored replay, concurrent 409, payload mismatch, and missing keys. The production section also covers the Redis 0.1.0 blocker and the crash window around external side effects.
-
A timed-out POST can still commit. Retrying it may create a second order, payment, or fulfillment request.
I built a Quarkus checkout demo around the HTTP Idempotency extension and tested the full state machine: first request, stored replay, concurrent 409, payload mismatch, and missing keys. The production section also covers the Redis 0.1.0 blocker and the crash window around external side effects.
-
A timed-out POST can still commit. Retrying it may create a second order, payment, or fulfillment request.
I built a Quarkus checkout demo around the HTTP Idempotency extension and tested the full state machine: first request, stored replay, concurrent 409, payload mismatch, and missing keys. The production section also covers the Redis 0.1.0 blocker and the crash window around external side effects.
-
A timed-out POST can still commit. Retrying it may create a second order, payment, or fulfillment request.
I built a Quarkus checkout demo around the HTTP Idempotency extension and tested the full state machine: first request, stored replay, concurrent 409, payload mismatch, and missing keys. The production section also covers the Redis 0.1.0 blocker and the crash window around external side effects.
-
Сердце облачной Java: проверяем Quarkus
Java уже какое-то время витает в облаках. Всё больше приложений и сервисов переходят на облачную архитектуру. Мы решили не отставать и проверить один из главных проектов для разработки производительных облачных приложений на Java — Quarkus.
-
Сердце облачной Java: проверяем Quarkus
Java уже какое-то время витает в облаках. Всё больше приложений и сервисов переходят на облачную архитектуру. Мы решили не отставать и проверить один из главных проектов для разработки производительных облачных приложений на Java — Quarkus.
-
Сердце облачной Java: проверяем Quarkus
Java уже какое-то время витает в облаках. Всё больше приложений и сервисов переходят на облачную архитектуру. Мы решили не отставать и проверить один из главных проектов для разработки производительных облачных приложений на Java — Quarkus.
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #255: Faster, Leaner, Predictable: Quarkus in the real world with Alexandru-Cătălin Diniș.
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #255: Faster, Leaner, Predictable: Quarkus in the real world with Alexandru-Cătălin Diniș.
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #255: Faster, Leaner, Predictable: Quarkus in the real world with Alexandru-Cătălin Diniș.
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #255: Faster, Leaner, Predictable: Quarkus in the real world with Alexandru-Cătălin Diniș.
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #255: Faster, Leaner, Predictable: Quarkus in the real world with Alexandru-Cătălin Diniș.
-
Join us next Monday, August 3rd, at 9am EST for Quarkus Insights Ep255. Are your technical decisions impacting your bottom line? Alexandru-Cătălin Diniș joins us to examine Quarkus through a FinOps lens to see how startup time and memory footprint influence your cloud costs. Perfect for architects and engineering leaders looking to build predictable, cost-efficient microservices.
-
Join us next Monday, August 3rd, at 9am EST for Quarkus Insights Ep255. Are your technical decisions impacting your bottom line? Alexandru-Cătălin Diniș joins us to examine Quarkus through a FinOps lens to see how startup time and memory footprint influence your cloud costs. Perfect for architects and engineering leaders looking to build predictable, cost-efficient microservices.
-
Join us next Monday, August 3rd, at 9am EST for Quarkus Insights Ep255. Are your technical decisions impacting your bottom line? Alexandru-Cătălin Diniș joins us to examine Quarkus through a FinOps lens to see how startup time and memory footprint influence your cloud costs. Perfect for architects and engineering leaders looking to build predictable, cost-efficient microservices.
-
Join us next Monday, August 3rd, at 9am EST for Quarkus Insights Ep255. Are your technical decisions impacting your bottom line? Alexandru-Cătălin Diniș joins us to examine Quarkus through a FinOps lens to see how startup time and memory footprint influence your cloud costs. Perfect for architects and engineering leaders looking to build predictable, cost-efficient microservices.
-
Join us next Monday, August 3rd, at 9am EST for Quarkus Insights Ep255. Are your technical decisions impacting your bottom line? Alexandru-Cătălin Diniș joins us to examine Quarkus through a FinOps lens to see how startup time and memory footprint influence your cloud costs. Perfect for architects and engineering leaders looking to build predictable, cost-efficient microservices.
-
Our next #JCON2026 session is live: 'Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design' with Rijo Sam
The Problem: Modern #Java applications often become prisoners of their #frameworks. While tools like #SpringBoot and #Quarkus …
Grab your coffee and hit play: https://youtu.be/4vVRqh_g4TU
-
Our next #JCON2026 session is live: 'Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design' with Rijo Sam
The Problem: Modern #Java applications often become prisoners of their #frameworks. While tools like #SpringBoot and #Quarkus …
Grab your coffee and hit play: https://youtu.be/4vVRqh_g4TU
-
Our next #JCON2026 session is live: 'Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design' with Rijo Sam
The Problem: Modern #Java applications often become prisoners of their #frameworks. While tools like #SpringBoot and #Quarkus …
Grab your coffee and hit play: https://youtu.be/4vVRqh_g4TU
-
Our next #JCON2026 session is live: 'Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design' with Rijo Sam
The Problem: Modern #Java applications often become prisoners of their #frameworks. While tools like #SpringBoot and #Quarkus …
Grab your coffee and hit play: https://youtu.be/4vVRqh_g4TU
-
Our next #JCON2026 session is live: 'Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design' with Rijo Sam
The Problem: Modern #Java applications often become prisoners of their #frameworks. While tools like #SpringBoot and #Quarkus …
Grab your coffee and hit play: https://youtu.be/4vVRqh_g4TU
-
I know Maven well. Gradle was mostly unfamiliar, so I built one Quarkus project to see where the difference becomes real.
A custom task generates build metadata, declares its inputs and output, joins `processResources`, and becomes `UP-TO-DATE` on the second run. The Java stays ordinary; the build model changes.
https://www.the-main-thread.com/p/quarkus-gradle-for-maven-developers
-
I know Maven well. Gradle was mostly unfamiliar, so I built one Quarkus project to see where the difference becomes real.
A custom task generates build metadata, declares its inputs and output, joins `processResources`, and becomes `UP-TO-DATE` on the second run. The Java stays ordinary; the build model changes.
https://www.the-main-thread.com/p/quarkus-gradle-for-maven-developers
-
I know Maven well. Gradle was mostly unfamiliar, so I built one Quarkus project to see where the difference becomes real.
A custom task generates build metadata, declares its inputs and output, joins `processResources`, and becomes `UP-TO-DATE` on the second run. The Java stays ordinary; the build model changes.
https://www.the-main-thread.com/p/quarkus-gradle-for-maven-developers
-
I know Maven well. Gradle was mostly unfamiliar, so I built one Quarkus project to see where the difference becomes real.
A custom task generates build metadata, declares its inputs and output, joins `processResources`, and becomes `UP-TO-DATE` on the second run. The Java stays ordinary; the build model changes.
https://www.the-main-thread.com/p/quarkus-gradle-for-maven-developers
-
I know Maven well. Gradle was mostly unfamiliar, so I built one Quarkus project to see where the difference becomes real.
A custom task generates build metadata, declares its inputs and output, joins `processResources`, and becomes `UP-TO-DATE` on the second run. The Java stays ordinary; the build model changes.
https://www.the-main-thread.com/p/quarkus-gradle-for-maven-developers
-
JDK 25 gives Quarkus services another startup option: train an AOT cache, keep the JVM, and reuse class-loading, linking, and method-profile data on the next run.
I built the full path with PostgreSQL and Podman: packaged training test, strict cache verification, a 20-run benchmark, and a target-specific container image. Local median readiness dropped from 1022.4 ms to 380.3 ms.
https://www.the-main-thread.com/p/quarkus-project-leyden-aot-cache
-
JDK 25 gives Quarkus services another startup option: train an AOT cache, keep the JVM, and reuse class-loading, linking, and method-profile data on the next run.
I built the full path with PostgreSQL and Podman: packaged training test, strict cache verification, a 20-run benchmark, and a target-specific container image. Local median readiness dropped from 1022.4 ms to 380.3 ms.
https://www.the-main-thread.com/p/quarkus-project-leyden-aot-cache
-
JDK 25 gives Quarkus services another startup option: train an AOT cache, keep the JVM, and reuse class-loading, linking, and method-profile data on the next run.
I built the full path with PostgreSQL and Podman: packaged training test, strict cache verification, a 20-run benchmark, and a target-specific container image. Local median readiness dropped from 1022.4 ms to 380.3 ms.
https://www.the-main-thread.com/p/quarkus-project-leyden-aot-cache
-
JDK 25 gives Quarkus services another startup option: train an AOT cache, keep the JVM, and reuse class-loading, linking, and method-profile data on the next run.
I built the full path with PostgreSQL and Podman: packaged training test, strict cache verification, a 20-run benchmark, and a target-specific container image. Local median readiness dropped from 1022.4 ms to 380.3 ms.
https://www.the-main-thread.com/p/quarkus-project-leyden-aot-cache
-
JDK 25 gives Quarkus services another startup option: train an AOT cache, keep the JVM, and reuse class-loading, linking, and method-profile data on the next run.
I built the full path with PostgreSQL and Podman: packaged training test, strict cache verification, a 20-run benchmark, and a target-specific container image. Local median readiness dropped from 1022.4 ms to 380.3 ms.
https://www.the-main-thread.com/p/quarkus-project-leyden-aot-cache
-
No Quarkus Insights today, but we'll be back next Monday, August 3rd, for a new session!
-
No Quarkus Insights today, but we'll be back next Monday, August 3rd, for a new session!
-
No Quarkus Insights today, but we'll be back next Monday, August 3rd, for a new session!
-
No Quarkus Insights today, but we'll be back next Monday, August 3rd, for a new session!
-
No Quarkus Insights today, but we'll be back next Monday, August 3rd, for a new session!
-
We're taking an additional holiday this coming Monday so no new Insights podcast but we'll be back August 3rd with a new session.
-
We're taking an additional holiday this coming Monday so no new Insights podcast but we'll be back August 3rd with a new session.
-
We're taking an additional holiday this coming Monday so no new Insights podcast but we'll be back August 3rd with a new session.
-
We're taking an additional holiday this coming Monday so no new Insights podcast but we'll be back August 3rd with a new session.
-
We're taking an additional holiday this coming Monday so no new Insights podcast but we'll be back August 3rd with a new session.
-
An upload bar reaching 100% proves that the bytes arrived. It says nothing about validation, importing, publication, or failure.
I rebuilt the pattern in Quarkus with two clocks: browser transfer progress, then a PostgreSQL-backed job processed by Scheduler and streamed over SSE. Reload-safe, cancellable, and honest about phases where no useful percentage exists.
https://www.the-main-thread.com/p/quarkus-long-running-job-progress-sse
-
An upload bar reaching 100% proves that the bytes arrived. It says nothing about validation, importing, publication, or failure.
I rebuilt the pattern in Quarkus with two clocks: browser transfer progress, then a PostgreSQL-backed job processed by Scheduler and streamed over SSE. Reload-safe, cancellable, and honest about phases where no useful percentage exists.
https://www.the-main-thread.com/p/quarkus-long-running-job-progress-sse
-
An upload bar reaching 100% proves that the bytes arrived. It says nothing about validation, importing, publication, or failure.
I rebuilt the pattern in Quarkus with two clocks: browser transfer progress, then a PostgreSQL-backed job processed by Scheduler and streamed over SSE. Reload-safe, cancellable, and honest about phases where no useful percentage exists.
https://www.the-main-thread.com/p/quarkus-long-running-job-progress-sse
-
An upload bar reaching 100% proves that the bytes arrived. It says nothing about validation, importing, publication, or failure.
I rebuilt the pattern in Quarkus with two clocks: browser transfer progress, then a PostgreSQL-backed job processed by Scheduler and streamed over SSE. Reload-safe, cancellable, and honest about phases where no useful percentage exists.
https://www.the-main-thread.com/p/quarkus-long-running-job-progress-sse
-
An upload bar reaching 100% proves that the bytes arrived. It says nothing about validation, importing, publication, or failure.
I rebuilt the pattern in Quarkus with two clocks: browser transfer progress, then a PostgreSQL-backed job processed by Scheduler and streamed over SSE. Reload-safe, cancellable, and honest about phases where no useful percentage exists.
https://www.the-main-thread.com/p/quarkus-long-running-job-progress-sse
-
Vault's TOTP API can validate a six-digit code. That is not yet a complete MFA flow.
This Quarkus tutorial adds the missing boundaries: authenticated subject, stored enrollment mapping, strict input validation, a two-minute step-up JWT, normal RBAC, and a replay test against a patched Vault runtime.
https://www.the-main-thread.com/p/quarkus-vault-totp-step-up-auth
-
Vault's TOTP API can validate a six-digit code. That is not yet a complete MFA flow.
This Quarkus tutorial adds the missing boundaries: authenticated subject, stored enrollment mapping, strict input validation, a two-minute step-up JWT, normal RBAC, and a replay test against a patched Vault runtime.
https://www.the-main-thread.com/p/quarkus-vault-totp-step-up-auth
-
Vault's TOTP API can validate a six-digit code. That is not yet a complete MFA flow.
This Quarkus tutorial adds the missing boundaries: authenticated subject, stored enrollment mapping, strict input validation, a two-minute step-up JWT, normal RBAC, and a replay test against a patched Vault runtime.
https://www.the-main-thread.com/p/quarkus-vault-totp-step-up-auth
-
Vault's TOTP API can validate a six-digit code. That is not yet a complete MFA flow.
This Quarkus tutorial adds the missing boundaries: authenticated subject, stored enrollment mapping, strict input validation, a two-minute step-up JWT, normal RBAC, and a replay test against a patched Vault runtime.
https://www.the-main-thread.com/p/quarkus-vault-totp-step-up-auth
-
Vault's TOTP API can validate a six-digit code. That is not yet a complete MFA flow.
This Quarkus tutorial adds the missing boundaries: authenticated subject, stored enrollment mapping, strict input validation, a two-minute step-up JWT, normal RBAC, and a replay test against a patched Vault runtime.
https://www.the-main-thread.com/p/quarkus-vault-totp-step-up-auth
-
Sorry, we're on holiday so no Quarkus Insights today. Join us in two weeks for a new session!
-
Sorry, we're on holiday so no Quarkus Insights today. Join us in two weeks for a new session!
-
Sorry, we're on holiday so no Quarkus Insights today. Join us in two weeks for a new session!
-
Sorry, we're on holiday so no Quarkus Insights today. Join us in two weeks for a new session!
-
Sorry, we're on holiday so no Quarkus Insights today. Join us in two weeks for a new session!
-
MCP tool authorization should not depend on the model following an instruction.
This builds a Quarkus MCP server where OPA evaluates skill manifests and caller context — trust tier, signature status, team, scopes — before a tool appears in tools/list or executes.
Rego compiles to Wasm and evaluates in-process. No sidecar, no network call. Each decision logs a policy version and reason codes.
-
MCP tool authorization should not depend on the model following an instruction.
This builds a Quarkus MCP server where OPA evaluates skill manifests and caller context — trust tier, signature status, team, scopes — before a tool appears in tools/list or executes.
Rego compiles to Wasm and evaluates in-process. No sidecar, no network call. Each decision logs a policy version and reason codes.