Blog Quarkus Newsletter #72 - September

September 16, 2026 #newsletter

Quarkus Newsletter #72 - September

James Cobb avatar James Cobb

Read Markus Eisele’s "Build Token Exchange Between Three Quarkus Services" to follow a user token from the order service to inventory and audit, then test why each service rejects a token meant for another audience. Learn how to integrate Quarkus, LangChain4j, and a large language model to generate custom poetry in "Create your first generative AI Java application with Quarkus and LangChain4j" by Laura Cowen. Quarkus 4 raises the Java baseline to 21. Check out "Java 21: the foundation for Quarkus 4" by Clement Escoffier to see why we made this choice and what it means for you. Check out this two part series from Daniel Oh. Check out "Part 1: Building Governed MCP Tool Services With Quarkus LangChain4j and Goose" to see how. To build governed, cloud-native Java MCP tool services for Goose agents using Quarkus LangChain4j, Java 25, and Jakarta Bean Validation. Then read "Part 2: Securing and Scaling Goose-to-Java Agent Traffic With agentgateway" learn now to deploy agentgateway as a security proxy between Goose AI agents and Quarkus MCP servers to enforce JWT auth, RBAC, and tool-poisoning guardrails.

You will also see the latest Quarkus Insights episodes, top social posts and upcoming Quarkus attended events.

Check out Newsletter #72: September!

Want to get newsletters in your inbox? Sign up for the newsletter using the on page form.

Quarkus is open. All dependencies of this project are available under the Apache Software License 2.0 or compatible license. CC by 3.0

This website was built with Roq on Quarkus, is hosted on GitHub Pages and is completely open source. If you want to make it better, fork the website and show us what you’ve got.

Navigation
Follow Us
Get Help
Languages
Quarkus is made of community projects
Copyright © Quarkus. All rights reserved. For details on our trademarks, please visit our Trademark Policy and Trademark List. Trademarks of third parties are owned by their respective holders and their mention here does not suggest any endorsement or association.