#quarkus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #quarkus, aggregated by home.social.
-
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.
-
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.
-
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.
-
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.
-
#AI can query your DB—but can it do it correctly? That’s the hard part. @MarcoBelladelli shows how #Hibernate + #Quarkus + #LangChain4j add validation & control back. Want fewer production surprises?
Dive in: https://javapro.io/2026/04/03/talk-to-your-data-natural-language-data-access-in-java/
-
#AI can query your DB—but can it do it correctly? That’s the hard part. @MarcoBelladelli shows how #Hibernate + #Quarkus + #LangChain4j add validation & control back. Want fewer production surprises?
Dive in: https://javapro.io/2026/04/03/talk-to-your-data-natural-language-data-access-in-java/
-
#AI can query your DB—but can it do it correctly? That’s the hard part. @MarcoBelladelli shows how #Hibernate + #Quarkus + #LangChain4j add validation & control back. Want fewer production surprises?
Dive in: https://javapro.io/2026/04/03/talk-to-your-data-natural-language-data-access-in-java/
-
Java в эпоху ИИ. К чему пришли на пятом MTC Web Services Meetup для разработчиков
Еще несколько лет назад разработчики на Java в основном обсуждали новые инструменты для создания программ, особенности архитектуры приложений и способы сделать сервисы быстрее и надежнее. Сегодня к этим темам добавился еще один важный вопрос — как искусственный интеллект меняет профессию программиста. Именно с этого началась пятая встреча в рамках MTC Web Services Meetup, которая собрала в Москве Java-разработчиков, архитекторов и инженеров. Вместо привычной серии докладов организаторы открыли вечер большой дискуссией о том, как меняется современная разработка, чему теперь стоит учиться, какую роль играют ИИ-ассистенты и как их использование влияет на безопасность решений. Обо всем этом — в материале. Читать дальше
https://habr.com/ru/companies/ru_mts/articles/1059050/
#разработка #Retry_Policy #Spring_Data_JPA #производительность #Quarkus #митап #тренды_java #мтс_true_tech
-
Java в эпоху ИИ. К чему пришли на пятом MTC Web Services Meetup для разработчиков
Еще несколько лет назад разработчики на Java в основном обсуждали новые инструменты для создания программ, особенности архитектуры приложений и способы сделать сервисы быстрее и надежнее. Сегодня к этим темам добавился еще один важный вопрос — как искусственный интеллект меняет профессию программиста. Именно с этого началась пятая встреча в рамках MTC Web Services Meetup, которая собрала в Москве Java-разработчиков, архитекторов и инженеров. Вместо привычной серии докладов организаторы открыли вечер большой дискуссией о том, как меняется современная разработка, чему теперь стоит учиться, какую роль играют ИИ-ассистенты и как их использование влияет на безопасность решений. Обо всем этом — в материале. Читать дальше
https://habr.com/ru/companies/ru_mts/articles/1059050/
#разработка #Retry_Policy #Spring_Data_JPA #производительность #Quarkus #митап #тренды_java #мтс_true_tech
-
Java в эпоху ИИ. К чему пришли на пятом MTC Web Services Meetup для разработчиков
Еще несколько лет назад разработчики на Java в основном обсуждали новые инструменты для создания программ, особенности архитектуры приложений и способы сделать сервисы быстрее и надежнее. Сегодня к этим темам добавился еще один важный вопрос — как искусственный интеллект меняет профессию программиста. Именно с этого началась пятая встреча в рамках MTC Web Services Meetup, которая собрала в Москве Java-разработчиков, архитекторов и инженеров. Вместо привычной серии докладов организаторы открыли вечер большой дискуссией о том, как меняется современная разработка, чему теперь стоит учиться, какую роль играют ИИ-ассистенты и как их использование влияет на безопасность решений. Обо всем этом — в материале. Читать дальше
https://habr.com/ru/companies/ru_mts/articles/1059050/
#разработка #Retry_Policy #Spring_Data_JPA #производительность #Quarkus #митап #тренды_java #мтс_true_tech
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #254 with Jeremy Davis for "Domain Driven Design and Hexagonal Architecture - Part 2"
http://bit.ly/quarkusinsights -
⏰ Starting soon! Join us for Quarkus Insights Ep. #254 with Jeremy Davis for "Domain Driven Design and Hexagonal Architecture - Part 2"
http://bit.ly/quarkusinsights -
⏰ Starting soon! Join us for Quarkus Insights Ep. #254 with Jeremy Davis for "Domain Driven Design and Hexagonal Architecture - Part 2"
http://bit.ly/quarkusinsights -
⏰ Starting soon! Join us for Quarkus Insights Ep. #254 with Jeremy Davis for "Domain Driven Design and Hexagonal Architecture - Part 2"
http://bit.ly/quarkusinsights -
⏰ Starting soon! Join us for Quarkus Insights Ep. #254 with Jeremy Davis for "Domain Driven Design and Hexagonal Architecture - Part 2"
http://bit.ly/quarkusinsights -
Jib can put a Quarkus fast-jar on a small runtime image without a Dockerfile. That is the easy part.
The useful checks come afterward: Java 25, UID 65532, a direct Java entrypoint, no shell, stable application layers, and an amd64/arm64 manifest.
I worked through the full path with Red Hat Hummingbird and Podman:
-
Jib can put a Quarkus fast-jar on a small runtime image without a Dockerfile. That is the easy part.
The useful checks come afterward: Java 25, UID 65532, a direct Java entrypoint, no shell, stable application layers, and an amd64/arm64 manifest.
I worked through the full path with Red Hat Hummingbird and Podman:
-
Jib can put a Quarkus fast-jar on a small runtime image without a Dockerfile. That is the easy part.
The useful checks come afterward: Java 25, UID 65532, a direct Java entrypoint, no shell, stable application layers, and an amd64/arm64 manifest.
I worked through the full path with Red Hat Hummingbird and Podman:
-
Jib can put a Quarkus fast-jar on a small runtime image without a Dockerfile. That is the easy part.
The useful checks come afterward: Java 25, UID 65532, a direct Java entrypoint, no shell, stable application layers, and an amd64/arm64 manifest.
I worked through the full path with Red Hat Hummingbird and Podman:
-
Jib can put a Quarkus fast-jar on a small runtime image without a Dockerfile. That is the easy part.
The useful checks come afterward: Java 25, UID 65532, a direct Java entrypoint, no shell, stable application layers, and an amd64/arm64 manifest.
I worked through the full path with Red Hat Hummingbird and Podman:
-
510 daily posts on The Main Thread taught me two things: consistency works, and agents only help when verification keeps up.
I am changing the cadence now. Still Quarkus, Java, standards, and agentic engineering. More room for tests, examples, and claims that earned their confidence.
-
510 daily posts on The Main Thread taught me two things: consistency works, and agents only help when verification keeps up.
I am changing the cadence now. Still Quarkus, Java, standards, and agentic engineering. More room for tests, examples, and claims that earned their confidence.
-
510 daily posts on The Main Thread taught me two things: consistency works, and agents only help when verification keeps up.
I am changing the cadence now. Still Quarkus, Java, standards, and agentic engineering. More room for tests, examples, and claims that earned their confidence.
-
510 daily posts on The Main Thread taught me two things: consistency works, and agents only help when verification keeps up.
I am changing the cadence now. Still Quarkus, Java, standards, and agentic engineering. More room for tests, examples, and claims that earned their confidence.
-
510 daily posts on The Main Thread taught me two things: consistency works, and agents only help when verification keeps up.
I am changing the cadence now. Still Quarkus, Java, standards, and agentic engineering. More room for tests, examples, and claims that earned their confidence.
-
Join us next Monday, July 13th, at 9am EST for Quarkus Insights Ep. 254 as Jeremy Davis returns to continue his discussion about building scalable monoliths with Quarkus, Domain-Driven Design, and Hexagonal Architecture.
-
Join us next Monday, July 13th, at 9am EST for Quarkus Insights Ep. 254 as Jeremy Davis returns to continue his discussion about building scalable monoliths with Quarkus, Domain-Driven Design, and Hexagonal Architecture.
-
Join us next Monday, July 13th, at 9am EST for Quarkus Insights Ep. 254 as Jeremy Davis returns to continue his discussion about building scalable monoliths with Quarkus, Domain-Driven Design, and Hexagonal Architecture.
-
Join us next Monday, July 13th, at 9am EST for Quarkus Insights Ep. 254 as Jeremy Davis returns to continue his discussion about building scalable monoliths with Quarkus, Domain-Driven Design, and Hexagonal Architecture.
-
Join us next Monday, July 13th, at 9am EST for Quarkus Insights Ep. 254 as Jeremy Davis returns to continue his discussion about building scalable monoliths with Quarkus, Domain-Driven Design, and Hexagonal Architecture.
-
Quarkus is a brutal repo for coding agents. Deployment, runtime, generated classes, and build items do not line up with grep.
I indexed the full platform tree with codebase-memory-mcp and ran the same @ConfigMapping trace in IBM Bob twice: grep versus graph MCP. Both got the answer. The graph path used fewer files and less context.
https://www.the-main-thread.com/p/quarkus-codebase-memory-mcp