#quarkus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #quarkus, aggregated by home.social.
-
Everybody loves a token chart. I care more about the app that boots.
This piece looks at a small Quarkus Agent MCP test thread and the part I think matters most: skills pay off when they cut wrong turns, retries, and stale framework guesses.
-
Everybody loves a token chart. I care more about the app that boots.
This piece looks at a small Quarkus Agent MCP test thread and the part I think matters most: skills pay off when they cut wrong turns, retries, and stale framework guesses.
-
Everybody loves a token chart. I care more about the app that boots.
This piece looks at a small Quarkus Agent MCP test thread and the part I think matters most: skills pay off when they cut wrong turns, retries, and stale framework guesses.
-
Everybody loves a token chart. I care more about the app that boots.
This piece looks at a small Quarkus Agent MCP test thread and the part I think matters most: skills pay off when they cut wrong turns, retries, and stale framework guesses.
-
Everybody loves a token chart. I care more about the app that boots.
This piece looks at a small Quarkus Agent MCP test thread and the part I think matters most: skills pay off when they cut wrong turns, retries, and stale framework guesses.
-
Finally live! Our training playlists are now public—covering #SpringBoot #Quarkus #Helidon #Payara #EclipseStore #Microstream
👉 Learn fundamentals that power modern Java
👉 Understand today’s frameworks
👉 Level up your backend skillsGet the free link: https://javapro.io/2026/04/01/new-java-training-playlists-now-available-from-fundamentals-to-modern-frameworks/
-
JVM Quarkus builds have been carrying dead dependency bytecode for years, and 3.35 finally gives us a packaging-time knife.
I put together a small Helios demo that measures fast-jar before and after tree shaking, reads the JarTreeShaker output, and shows where excluded-artifacts enters the story.
-
JVM Quarkus builds have been carrying dead dependency bytecode for years, and 3.35 finally gives us a packaging-time knife.
I put together a small Helios demo that measures fast-jar before and after tree shaking, reads the JarTreeShaker output, and shows where excluded-artifacts enters the story.
-
JVM Quarkus builds have been carrying dead dependency bytecode for years, and 3.35 finally gives us a packaging-time knife.
I put together a small Helios demo that measures fast-jar before and after tree shaking, reads the JarTreeShaker output, and shows where excluded-artifacts enters the story.
-
JVM Quarkus builds have been carrying dead dependency bytecode for years, and 3.35 finally gives us a packaging-time knife.
I put together a small Helios demo that measures fast-jar before and after tree shaking, reads the JarTreeShaker output, and shows where excluded-artifacts enters the story.
-
Every deterministic workflow step does not need a planner call.
This piece shows how to keep MCP tools boring inside a LangChain4j graph: one Quarkus MCP server, one workflow app, /topology, and tests that hit real Ollama instead of stubs.
https://www.the-main-thread.com/p/quarkus-langchain4j-mcp-tool-agents
-
Every deterministic workflow step does not need a planner call.
This piece shows how to keep MCP tools boring inside a LangChain4j graph: one Quarkus MCP server, one workflow app, /topology, and tests that hit real Ollama instead of stubs.
https://www.the-main-thread.com/p/quarkus-langchain4j-mcp-tool-agents
-
Every deterministic workflow step does not need a planner call.
This piece shows how to keep MCP tools boring inside a LangChain4j graph: one Quarkus MCP server, one workflow app, /topology, and tests that hit real Ollama instead of stubs.
https://www.the-main-thread.com/p/quarkus-langchain4j-mcp-tool-agents
-
Every deterministic workflow step does not need a planner call.
This piece shows how to keep MCP tools boring inside a LangChain4j graph: one Quarkus MCP server, one workflow app, /topology, and tests that hit real Ollama instead of stubs.
https://www.the-main-thread.com/p/quarkus-langchain4j-mcp-tool-agents
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #247 for Agentic Orchestration with Quarkus, LangChain4j, and Kubernetes with Jonathan Johnson.
-
Outbound REST client logs are where bearer tokens go to become incident notes if you are careless.
This post shows how Quarkus masked-headers really behaves, why setting the property replaces the default list, and how to prove the safe path with @QuarkusTestProfile.
https://www.the-main-thread.com/p/quarkus-rest-client-header-masking
-
Agent demos love static diagrams. Production gives you a different graph.
This post shows how to expose a live LangChain4j topology from Quarkus with AgentMonitor, HtmlReportGenerator, and an SSE feed for recent runs.
https://www.the-main-thread.com/p/quarkus-langchain4j-topology-http
-
Agent names are not a routing strategy.
This walkthrough builds a Quarkus + LangChain4j sample that uses filesystem Skills to make ownership explicit, keeps a baseline supervisor for comparison, and proves the routing with HTTP tests.
-
Minecraft for observability #quarkus #podcast #minecraft
Holly Cummins found a unwritten extension for Quarkus, and created observability by chicken explosions.An excerpt from Kodsnack 701 - listen where you get podcasts, or at kodsnack.se!
-
Once a tool-calling assistant grows from 5 tools to 50, the problem stops being “prompting” and starts being context geometry.
This walkthrough builds a Quarkus + LangChain4j + Ollama example and shows what tool search actually changes: smaller working sets, visible search rounds, and more prompt headroom even when local latency is messy.
https://www.the-main-thread.com/p/langchain4j-tool-search-quarkus-ollama
-
Yesterday I tried to demo Quarkus Agent MCP with IBM Bob.
Podman was not running, the app leaned on Dev Services, and Bob started reading an infrastructure failure like it might be a code problem. Annoying demo. Useful lesson.
I wrote up what Quarkus Agent MCP actually adds, and how that failure already turned into a better tool.
-
In this #InfoQ #podcast, Andy Damevin (long-time Quarkus contributor) explores #Roq - a static site generator built on top of #Quarkus.
He covers:
• The motivation behind the project
• Why Java & Quarkus were chosen
• Migration to Roq
• Its future direction🎧 Listen now: https://bit.ly/4n6MiKQ
📄 #transcript included -
In this #InfoQ #podcast, Andy Damevin (long-time Quarkus contributor) explores #Roq - a static site generator built on top of #Quarkus.
He covers:
• The motivation behind the project
• Why Java & Quarkus were chosen
• Migration to Roq
• Its future direction🎧 Listen now: https://bit.ly/4n6MiKQ
📄 #transcript included -
In this #InfoQ #podcast, Andy Damevin (long-time Quarkus contributor) explores #Roq - a static site generator built on top of #Quarkus.
He covers:
• The motivation behind the project
• Why Java & Quarkus were chosen
• Migration to Roq
• Its future direction🎧 Listen now: https://bit.ly/4n6MiKQ
📄 #transcript included -
In this #InfoQ #podcast, Andy Damevin (long-time Quarkus contributor) explores #Roq - a static site generator built on top of #Quarkus.
He covers:
• The motivation behind the project
• Why Java & Quarkus were chosen
• Migration to Roq
• Its future direction🎧 Listen now: https://bit.ly/4n6MiKQ
📄 #transcript included -
In this #InfoQ #podcast, Andy Damevin (long-time Quarkus contributor) explores #Roq - a static site generator built on top of #Quarkus.
He covers:
• The motivation behind the project
• Why Java & Quarkus were chosen
• Migration to Roq
• Its future direction🎧 Listen now: https://bit.ly/4n6MiKQ
📄 #transcript included -
⏰ Starting soon! Join us for Quarkus Insights Ep. #246 for Evolving Minecraft Into a Cloud Native Platform with Jaden Welderich & Austin Mayes.
http://bit.ly/quarkusinsights -
Join us next Monday, May 4th, at 9am EST for Quarkus Insights Ep. 246 as Jaden Welderich & Austin Mayes discuss transformed one of the world's largest Minecraft servers from a legacy monolith into a scalable, cloud native game platform on OKD and Quarkus.
-
A brief introduction to Quarkus Flow http://quarkusguru.github.io/posts/a-brief-introduction-to-quarkus-flow/
-
You asked for it—it’s finally here! A full collection of #Java training videos: #SpringBoot #Quarkus #Helidon #Payara #EclipseStore #Microstream & ...
✔️ Build real understanding
✔️ Learn core concepts that still apply
✔️ Go beyond quick tutorials
Watch: https://www.youtube.com -
⏰ Starting soon! Join us for Quarkus Insights Ep. #245 as Julien Viet discusses HTTP/3 support coming in Vert.x 5.1.
-
Quarkus cache invalidation is success-only. That is correct, but it can surprise you when a method changes state and then throws.
I wrote a small pricing-service tutorial showing `@CacheResult` on `Uni`, `@CacheInvalidateAll`, lock-on-miss behavior, and the `CacheManager` escape hatch.
https://www.the-main-thread.com/p/quarkus-cache-failure-semantics
-
Quarkus can now give you a useful SBOM from the build itself, not just a Maven dependency tree with nicer stationery.
I wrote up the practical path: add `quarkus-cyclonedx`, build a tiny service, inspect the distribution SBOM, generate the dependency SBOM, validate both with the CycloneDX CLI, and archive them in CI.
Boring evidence is still evidence. I like that part.
-
Join us next Monday, April 27th, at 9am EST for Quarkus Insights Ep. 245 as Julien Viet discusses how Vert.x 5.1 supports HTTP/3 & the QUIC transport protocol to enhance web speed & security resulting in superior performance on modern networks.
-
RAG demos often start with clean Markdown, which is a suspiciously convenient place to begin.
This one starts with messy enterprise documents instead: Quarkus, Docling, pgvector, LangChain4j, Ollama, readiness checks, and guardrails in one local Java application.
https://www.the-main-thread.com/p/enterprise-rag-quarkus-docling
-
Exclusive Devoxx UK Discount for Quarkus Devs!
Want to catch all the supersonic, subatomic Java talks at Devoxx UK? Grab £50 off your registration with the exclusive code DVX26QUARKUS.
Don't miss the Quarkus sessions, and be sure to drop by the Quarkus Community Booth. Let's talk high-performance, cloud-native apps, and our latest Generative AI integrations with LangChain4j.
See you in London!
#DevoxxUK #Quarkus #Java #AI #LangChain4j #OpenSource #quarkusworldtour
-
Cheerio, London! The Quarkus community is heading to Devoxx UK on May 6th and 7th!
We are proud to sponsor a booth at this year's event in the Business Design Centre. Stop by to chat with our community members about how to supercharge your skillset with supersonic, subatomic Java. We'd love to talk to you about live coding, developer joy, & how to easily build enterprise-grade AI apps using our native LangChain4j integration!
️
See you there!
@DevoxxUK #DevoxxUK #Quarkus #Java #AI #LangChain4j -
I see many badge demos that stop at “store a row, serve a PNG, done.”
That works until trust matters.
In this tutorial, I built a Quarkus app that issues signed badge assertions, exposes public verification URLs, and protects partner webhooks with HMAC. The interesting part is the failure modes: composite keys, flush order, idempotency, and trust boundaries.
https://www.the-main-thread.com/p/build-digital-credentialing-platform-quarkus
-
⏰ Starting soon! Join us for Quarkus Insights Ep. #244: How We Benchmarked Quarkus with Holly Cummins, Eric Deandrea, & Francesco Nigro.
-
Java developers: this guest post by Sebastian Kühnau shows how to build a streaming AI chat with Quarkus, Vaadin Flow, and LangChain4j — all in plain Java. A nice example of token-by-token UI updates without switching to a separate frontend stack.
https://www.the-main-thread.com/p/streaming-ai-chat-java-quarkus-vaadin-langchain4j -
I took down one of my Quarkus posts.
Not because the whole thing was bad. A few answers were just off in a way that can mislead people. That is enough.
So I wrote about the part underneath it: how I try to keep AI-infused IDEs and writing workflows grounded in current docs, runnable code, and explicit guardrails.
Also a bit more personal than usual, because I think this part matters.
https://www.the-main-thread.com/p/quarkus-ai-grounding-java-writing-workflow
-
I took down one of my Quarkus posts.
Not because the whole thing was bad. A few answers were just off in a way that can mislead people. That is enough.
So I wrote about the part underneath it: how I try to keep AI-infused IDEs and writing workflows grounded in current docs, runnable code, and explicit guardrails.
Also a bit more personal than usual, because I think this part matters.
https://www.the-main-thread.com/p/quarkus-ai-grounding-java-writing-workflow
-
I took down one of my Quarkus posts.
Not because the whole thing was bad. A few answers were just off in a way that can mislead people. That is enough.
So I wrote about the part underneath it: how I try to keep AI-infused IDEs and writing workflows grounded in current docs, runnable code, and explicit guardrails.
Also a bit more personal than usual, because I think this part matters.
https://www.the-main-thread.com/p/quarkus-ai-grounding-java-writing-workflow
-
I took down one of my Quarkus posts.
Not because the whole thing was bad. A few answers were just off in a way that can mislead people. That is enough.
So I wrote about the part underneath it: how I try to keep AI-infused IDEs and writing workflows grounded in current docs, runnable code, and explicit guardrails.
Also a bit more personal than usual, because I think this part matters.
https://www.the-main-thread.com/p/quarkus-ai-grounding-java-writing-workflow
-
I took down one of my Quarkus posts.
Not because the whole thing was bad. A few answers were just off in a way that can mislead people. That is enough.
So I wrote about the part underneath it: how I try to keep AI-infused IDEs and writing workflows grounded in current docs, runnable code, and explicit guardrails.
Also a bit more personal than usual, because I think this part matters.
https://www.the-main-thread.com/p/quarkus-ai-grounding-java-writing-workflow
-
I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.
This piece is about that line.
For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.
https://www.the-main-thread.com/p/ai-coding-agents-security-java-blast-radius
#Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava
-
I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.
This piece is about that line.
For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.
https://www.the-main-thread.com/p/ai-coding-agents-security-java-blast-radius
#Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava
-
I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.
This piece is about that line.
For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.
https://www.the-main-thread.com/p/ai-coding-agents-security-java-blast-radius
#Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava
-
I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.
This piece is about that line.
For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.
https://www.the-main-thread.com/p/ai-coding-agents-security-java-blast-radius
#Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava