<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tutorials on foojay.io - Friends Of OpenJDK</title><link>https://foojay.io/today/category/tutorials/</link><description>Recent content in Tutorials on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://foojay.io/today/category/tutorials/index.xml" rel="self" type="application/rss+xml"/><item><title>Who Is Actually Turning Your Java Object Into JSON?</title><link>https://foojay.io/today/who-is-actually-turning-your-java-object-into-json/</link><pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/who-is-actually-turning-your-java-object-into-json/</guid><description>&lt;p&gt;A personal note before we start: I had been working on this post for a few days, but the recent &lt;a href="https://www.reuters.com/business/environment/panama-suffers-over-200-aftershocks-after-fridays-77-magnitude-earthquake-2026-10-11/" target="_blank" rel="noopener noreferrer"&gt;earthquake in Panama&lt;/a&gt; made it harder than expected to sit down and finish it. I’m glad to finally share it with you, and my thoughts are with everyone affected.&lt;/p&gt;&#10;&lt;p&gt;After some time away from the keyboard, I’m returning to a topic that is easy to take for granted in everyday Java development: JSON.&lt;/p&gt;</description></item><item><title>Analytics in the Browser with DuckDB-Wasm and a Java Backend</title><link>https://foojay.io/today/analytics-in-the-browser-with-duckdb-wasm/</link><pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/analytics-in-the-browser-with-duckdb-wasm/</guid><description>&lt;p&gt;&lt;em&gt;DuckDB-Wasm runs the DuckDB analytical database inside the browser tab. The Java backend sends the dataset once, and from then on each filter and aggregation is a local SQL query rather than another request to the server. Below is a two-file example with no build tools, and a look at when the approach is a good fit and when it isn&amp;rsquo;t.&lt;/em&gt;&lt;/p&gt;&#10;&lt;h2 id="every-click-is-a-round-trip"&gt;Every click is a round-trip&lt;/h2&gt;&#10;&lt;p&gt;Most Java web apps that show analytics follow the same pattern. The user picks a filter, the browser calls a REST endpoint, the Java service runs a &lt;code&gt;GROUP BY&lt;/code&gt; against the database, serialises the result to JSON, and sends it back. Change the date range: another round-trip. Switch from &amp;ldquo;by region&amp;rdquo; to &amp;ldquo;by product&amp;rdquo;: another one.&lt;/p&gt;</description></item><item><title>EUDI wallets with OpenID4VP and pac4j: same device and another device</title><link>https://foojay.io/today/eudi-wallets-openid4vp-pac4j/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/eudi-wallets-openid4vp-pac4j/</guid><description>&lt;p&gt;The European Digital Identity wallet is coming, and applications accepting it will need to talk to it. This tutorial brings wallet authentication to a Java Spring Boot application with pac4j, through two complete examples: a browser and wallet on the same phone, then a browser on a computer and a wallet on a phone, connected by a QR code.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://www.pac4j.org/" target="_blank" rel="noopener noreferrer"&gt;pac4j&lt;/a&gt; is an open-source Java security library for authentication and authorization across multiple web frameworks. I am Jérôme LELEU, its creator and maintainer. This article combines the two walkthroughs originally published on the pac4j blog: &lt;a href="https://www.pac4j.org/blog/openid4vp_in_action_same_device.html" target="_blank" rel="noopener noreferrer"&gt;on the same device&lt;/a&gt; and &lt;a href="https://www.pac4j.org/blog/openid4vp_in_action_another_device.html" target="_blank" rel="noopener noreferrer"&gt;on another device&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Batch Processing with MongoDB and Jakarta EE: From Customer Segmentation to Scalable Workflows</title><link>https://foojay.io/today/batch-processing-mongodb-jakarta-ee-customer-segmentation/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/batch-processing-mongodb-jakarta-ee-customer-segmentation/</guid><description>&lt;p&gt;Batch processing addresses a common enterprise need: reliably applying business rules to large data sets without relying on individual user requests. Tasks such as recalculating customer segments, migrating records, reconciling transactions, updating prices, or processing millions of documents require more than a basic loop. Applications must control memory efficiently, handle failures, minimize unnecessary writes, and separate long-running processes away from interactive user experiences.&lt;/p&gt;&#10;&lt;p&gt;MongoDB and Jakarta Batch work well jointly to address these needs. In this article, we will develop a customer segmentation workflow that allows an administrator to adjust spending thresholds for Bronze, Silver, Gold, and Platinum customers, preview the impact, and initiate a batch job to reclassify only the necessary records. Our focus goes beyond batch APIs to designing a clear, scalable workflow that connects business decisions to controlled data processing.&lt;/p&gt;</description></item><item><title>OpenID Federation with pac4j and CAS</title><link>https://foojay.io/today/openid-federation-with-pac4j-and-cas/</link><pubDate>Fri, 30 Oct 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/openid-federation-with-pac4j-and-cas/</guid><description>&lt;p&gt;OpenID Connect (OIDC) has become the go-to protocol for modern application login, progressively taking over many use cases previously handled by SAML or custom authentication built around OAuth. &lt;a href="https://openid.net/specs/openid-connect-core-1_0.html" target="_blank" rel="noopener noreferrer"&gt;OIDC adds a standardized identity layer on top of OAuth 2.0&lt;/a&gt;: OAuth provides delegated authorization, while OIDC also tells an application who has signed in.&lt;/p&gt;&#10;&lt;p&gt;The ecosystem has grown into a family of specifications covering many needs, from provider discovery and dynamic client registration to session management and logout. But one piece was still missing from that picture: a standard way to establish trust across an entire federation without separately onboarding every application at every identity provider. This is the problem addressed by &lt;a href="https://openid.net/specs/openid-federation-1_0.html" target="_blank" rel="noopener noreferrer"&gt;OpenID Federation&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>How to Secure a Spring Boot Application with OpenID Connect and pac4j</title><link>https://foojay.io/today/how-to-secure-a-spring-boot-application-with-openid-connect-and-pac4j/</link><pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/how-to-secure-a-spring-boot-application-with-openid-connect-and-pac4j/</guid><description>&lt;p&gt;&lt;a href="https://www.pac4j.org/" target="_blank" rel="noopener noreferrer"&gt;pac4j&lt;/a&gt; is an open-source Java security library for authentication and authorization. It supports protocols such as OpenID Connect, OAuth 2.0, SAML and CAS, with integrations for multiple Java web frameworks. I am Jérôme LELEU, the maintainer of pac4j. In this tutorial, we will use its OpenID Connect client with Spring Boot.&lt;/p&gt;&#10;&lt;p&gt;You want users to sign in to your Java application with Keycloak, Google, Microsoft Entra ID, Okta, Auth0 or even a CAS server. They already have an account there, so your application should not ask them for another password.&lt;/p&gt;</description></item><item><title>Java Stream Gatherers: From Built-in Patterns to Custom Pipeline Mechanics</title><link>https://foojay.io/today/java-stream-gatherers/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/java-stream-gatherers/</guid><description>&lt;h1 id="java-stream-gatherers-from-built-in-patterns-to-custom-pipeline-mechanics"&gt;Java Stream Gatherers: From Built-in Patterns to Custom Pipeline Mechanics&lt;/h1&gt;&#10;&lt;h2 id="table-of-contents"&gt;Table of Contents&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#1-introduction--context"&gt;1. Introduction &amp;amp; Context&lt;/a&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#11-the-evolution-of-streams"&gt;1.1 The Evolution of Streams&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#12-the-collector-problem"&gt;1.2 The &amp;ldquo;Collector Problem&amp;rdquo;&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#13-what-are-stream-gatherers"&gt;1.3 What are Stream Gatherers?&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#2-getting-started-built-in-gatherers-in-action"&gt;2. Getting Started: Built-In Gatherers in Action&lt;/a&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#21-understanding-stream-cardinality"&gt;2.1 Understanding Stream Cardinality&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#22-the-five-ready-to-use-gatherers"&gt;2.2 The Five Ready-to-Use Gatherers&lt;/a&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#221-batching-items-with-windowfixed"&gt;2.2.1 Batching Items with &lt;code&gt;windowFixed&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#222-analyzing-sequences-with-windowsliding"&gt;2.2.2 Analyzing Sequences with &lt;code&gt;windowSliding&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#223-accumulating-values-with-scan"&gt;2.2.3 Accumulating Values with &lt;code&gt;scan&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#224-intermediate-aggregations-with-fold"&gt;2.2.4 Intermediate Aggregations with &lt;code&gt;fold&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#225-bounded-parallelism-with-mapconcurrent"&gt;2.2.5 Bounded Parallelism with &lt;code&gt;mapConcurrent&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#3-leveling-up-from-using-gatherers-to-authoring-your-own"&gt;3. Leveling Up: From Using Gatherers to Authoring Your Own&lt;/a&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#31-when-should-you-write-a-custom-gatherer"&gt;3.1 When Should You Write a Custom Gatherer?&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#32-pipeline-composition-with-andthen"&gt;3.2 Pipeline Composition with &lt;code&gt;andThen()&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#4-under-the-hood-architecture--anatomy-of-custom-gatherers"&gt;4. Under the Hood: Architecture &amp;amp; Anatomy of Custom Gatherers&lt;/a&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#41-anatomy-of-a-gatherert-a-r"&gt;4.1 Anatomy of a &lt;code&gt;Gatherer&amp;lt;T, A, R&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#42-the-four-building-blocks-initializer-integrator-combiner-finisher"&gt;4.2 The Four Building Blocks (&lt;code&gt;initializer&lt;/code&gt;, &lt;code&gt;integrator&lt;/code&gt;, &lt;code&gt;combiner&lt;/code&gt;, &lt;code&gt;finisher&lt;/code&gt;)&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#43-concrete-walkthrough-building-a-custom-gatherer"&gt;4.3 Concrete Walkthrough: Building a Custom Gatherer&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#5-production-ready-gatherers-parallelism-state-and-pitfalls"&gt;5. Production-Ready Gatherers: Parallelism, State, and Pitfalls&lt;/a&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="#51-parallel-execution-modes--combiners"&gt;5.1 Parallel Execution Modes &amp;amp; Combiners&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#52-greedy-vs-short-circuiting-integrators"&gt;5.2 Greedy vs. Short-Circuiting Integrators&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#53-state-management--thread-safety"&gt;5.3 State Management &amp;amp; Thread Safety&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#54-gatherer-vs-collector-a-quick-comparison"&gt;5.4 Gatherer vs. Collector: A Quick Comparison&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#6-conclusion"&gt;6. Conclusion&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="#references"&gt;References&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr&gt;&#10;&lt;p&gt;&lt;img src="https://foojay.io/today/java-stream-gatherers/StreamGatherers.jpg" alt="Stream Gatherers" title="Stream Gatherers" width="1024" height="559" loading="lazy" decoding="async"&gt;&lt;/p&gt;</description></item><item><title>Build Your First SaaS with MongoDB Ephemeral Clusters</title><link>https://foojay.io/today/build-your-first-saas-with-mongodb-ephemeral-clusters/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/build-your-first-saas-with-mongodb-ephemeral-clusters/</guid><description>&lt;p&gt;It&amp;rsquo;s a new world. A prototype that once meant hours or days of setup can now be up and running in minutes. With one API call, an AI agent can create a MongoDB Atlas cluster from your IDE, so you can start building without stopping to navigate account setup, cloud choices, regions, or cluster configuration.&lt;/p&gt;&#10;&lt;p&gt;In this tutorial, you will use an &lt;a href="https://www.mongodb.com/products/tools/atlas-ephemeral-clusters/" target="_blank" rel="noopener noreferrer"&gt;Atlas Ephemeral Cluster&lt;/a&gt; to build a polished job-application tracker: a small SaaS where a user manages applications on a Kanban board. The application is deliberately simple. The point is the workflow: give an agent a real database immediately, validate an idea quickly, and claim the cluster only when the prototype is worth keeping.&lt;/p&gt;</description></item><item><title>World geography gotchas</title><link>https://foojay.io/today/world-geography-gotchas/</link><pubDate>Sun, 20 Sep 2026 05:51:17 +0000</pubDate><guid>https://foojay.io/today/world-geography-gotchas/</guid><description>&lt;p&gt;Years ago, a colleague of mine told me about two pockets of foreign land surrounded by Switzerland: &lt;a href="https://osm.org/go/0Ck2o6xg-" target="_blank" rel="noopener noreferrer"&gt;Campione d&amp;rsquo;Italia&lt;/a&gt; and &lt;a href="https://osm.org/go/0C1ZlDk" target="_blank" rel="noopener noreferrer"&gt;Büsingen am Hochrhein&lt;/a&gt;, respectively Italy and Germany. Both are &lt;em&gt;enclaves&lt;/em&gt; of their respective country in Swiss territory:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;An enclave is a part of the territory of a state that is enclosed within the territory of another state. To distinguish the parts of a state entirely enclosed in a single other state, they are called true enclaves. A true enclave cannot be reached without passing through the territory of a single other state that surrounds it.&lt;/p&gt;&#10;&lt;p&gt;—- &lt;a href="https://en.wikipedia.org/wiki/Enclave_and_exclave#True_enclaves" target="_blank" rel="noopener noreferrer"&gt;Enclave and exclave&lt;/a&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>Jakarta Faces, Java Web Framework, Stateless Edition: Marketplace AliFaces</title><link>https://foojay.io/today/jakarta-faces-java-web-framework-stateless-edition-marketplace-alifaces/</link><pubDate>Sat, 29 Aug 2026 19:22:52 +0000</pubDate><guid>https://foojay.io/today/jakarta-faces-java-web-framework-stateless-edition-marketplace-alifaces/</guid><description>&lt;h3 id="a-fully-stateless-jakarta-faces-marketplace-with-server-side-rendering--no-httpsession-no-saved-viewstate-no-sticky-sessions"&gt;A Fully Stateless Jakarta Faces Marketplace with Server-Side Rendering — No HttpSession, No Saved ViewState, No Sticky Sessions&lt;/h3&gt;&#10;&lt;p&gt;(see the poc on: &lt;a href="http://129.152.31.253:8080/alifaces" title="AliFaces POC Run On Oracle OCI" target="_blank" rel="noopener noreferrer"&gt;AliFaces POC Run On Oracle OCI(Nanos Unikernel)&lt;/a&gt;)&lt;/p&gt;&#10;&lt;p&gt;Jakarta Faces still carries a few persistent assumptions: it is stateful, it requires &lt;code&gt;HttpSession&lt;/code&gt;, it needs sticky sessions to scale horizontally, and its server-side rendering model belongs to an older generation of web applications.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;AliFaces&lt;/strong&gt; challenges those assumptions with running code — not a Hello World, but a marketplace-style application with catalog, search, filters, cart, checkout, orders, browsing history, themes, responsive layouts and a JSON API for mobile clients.&lt;/p&gt;</description></item><item><title>Offline Crypto Address Validation in Java</title><link>https://foojay.io/today/offline-crypto-address-validation-in-java/</link><pubDate>Sat, 22 Aug 2026 08:43:04 +0000</pubDate><guid>https://foojay.io/today/offline-crypto-address-validation-in-java/</guid><description>&lt;p&gt;Backend validation often starts with simple questions.&lt;/p&gt;&#10;&lt;p&gt;Is the input empty? Does it have the expected shape? Can it be parsed? Does it belong to the selected domain?&lt;/p&gt;&#10;&lt;p&gt;Crypto wallet addresses are no different, except the formats vary across chains and simple regular expressions are rarely enough.&lt;/p&gt;&#10;&lt;p&gt;If a Java backend accepts crypto withdrawal addresses, address-book entries, CSV imports, support-tool input, or transaction preflight requests, it should reject clearly invalid addresses before calling RPC nodes, explorers, exchange APIs, or internal money-movement systems.&lt;/p&gt;</description></item><item><title>Idempotent Write Paths: Keeping an Integration Pipeline Correct When Messages Repeat</title><link>https://foojay.io/today/idempotent-write-paths-keeping-an-integration-pipeline-correct-when-messages-repeat/</link><pubDate>Mon, 17 Aug 2026 06:46:00 +0000</pubDate><guid>https://foojay.io/today/idempotent-write-paths-keeping-an-integration-pipeline-correct-when-messages-repeat/</guid><description>&lt;h2 id="a-reconciliation-that-didnt-add-up"&gt;A reconciliation that didn&amp;rsquo;t add up&lt;/h2&gt;&#10;&lt;p&gt;Let me start with a real one. After a big sales promo, during reconciliation, finance said a batch of orders had the wrong status: on our side it showed &amp;ldquo;paid&amp;rdquo;, but the finance system hadn&amp;rsquo;t booked it.&lt;/p&gt;&#10;&lt;p&gt;Tracing it back, we found the payment gateway had retried during its peak, and the same payment notification got pushed twice. The first one was processed normally; the second time it came, the consumer happened to be in the middle of a rolling restart, so the message got re-queued and consumed again.&lt;/p&gt;</description></item><item><title>Idempotent Spring Boot: Safe REST with One Annotation</title><link>https://foojay.io/today/idempotent-spring-boot-starter/</link><pubDate>Tue, 04 Aug 2026 22:11:22 +0000</pubDate><guid>https://foojay.io/today/idempotent-spring-boot-starter/</guid><description>&lt;h2 id="idempotent-rest-endpoints-without-the-boilerplate"&gt;Idempotent REST Endpoints Without the Boilerplate&lt;/h2&gt;&#10;&lt;h2 id="stop-charging-your-users-twice-idempotent-rest-endpoints-with-one-annotation"&gt;Stop Charging Your Users Twice: Idempotent REST Endpoints with One Annotation&lt;/h2&gt;&#10;&lt;h2 id="the-problem-nobody-talks-about-until-production"&gt;The problem nobody talks about until production&lt;/h2&gt;&#10;&lt;p&gt;A user taps &amp;ldquo;Pay.&amp;rdquo; The request times out. Their app retries. Your server charges them twice.&lt;/p&gt;&#10;&lt;p&gt;You didn&amp;rsquo;t write a bug. The network did. But your users don&amp;rsquo;t care about that distinction.&lt;/p&gt;&#10;&lt;p&gt;The idempotency problem shows up in more places than payments. A load balancer replays a timed-out request. A mobile client double-taps a submit button. A Kubernetes pod retries after a restart. From the server&amp;rsquo;s perspective, all of these look identical: a second POST that arrives after the first one already executed.&lt;/p&gt;</description></item><item><title>Getting Started with Exposed: Kotlin ORM Made Simple</title><link>https://foojay.io/today/exposed-kotlin-orm-complete-guide/</link><pubDate>Mon, 06 Jul 2026 03:39:00 +0000</pubDate><guid>https://foojay.io/today/exposed-kotlin-orm-complete-guide/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;For quite some time, I have been a huge fan of and fascinated by JetBrains products, tools, and libraries because of their masterful craftsmanship in product creation and their pristine focus on building high-quality developer tools.&lt;/p&gt;&#10;&lt;p&gt;Even more excitingly, JetBrains Java Annotated Monthly newsletters have featured most of the technical articles I wrote for Foojay on topics such as Java, Spring, Spring Boot 4, and OpenRewrite.&lt;/p&gt;&#10;&lt;p&gt;Recently, one Kotlin Domain-Specific Language (DSL) library caught my attention. I immediately tried converting my existing Spring Boot 4 application from Java to Kotlin using Exposed, an ORM framework for Kotlin.&#10;&lt;img src="https://foojay.io/today/exposed-kotlin-orm-complete-guide/Exposed-1024x683.jpg" alt="Exposed" width="1024" height="683" loading="lazy" decoding="async"&gt; Kotlin SQL Libary&lt;/p&gt;</description></item><item><title>Quarkus Unpacked: Insights from the Foojay Podcast</title><link>https://foojay.io/today/quarkus-unpacked-insights-from-the-foojay-podcast/</link><pubDate>Tue, 23 Jun 2026 12:36:54 +0000</pubDate><guid>https://foojay.io/today/quarkus-unpacked-insights-from-the-foojay-podcast/</guid><description>&lt;figure class="alignleft is-resized"&gt;&#10; &lt;img src="https://foojay.io/today/quarkus-unpacked-insights-from-the-foojay-podcast/3-Quarkus-Unpacked-2-2.jpeg" alt="Quarkus: A Runtime and Framework for Cloud-Native Java" style="width:300px" loading="lazy" class="is-zoomable"&gt;&lt;/figure&gt;&#10;&#10;&lt;p&gt;I recently had the pleasure of joining the &lt;a href="https://www.youtube.com/watch?v=_nJCTTrnZkE" target="_blank" rel="noopener noreferrer"&gt;Foojay podcast&lt;/a&gt; to talk about Quarkus in depth. The conversation covered a lot of ground, from what makes Quarkus different to the practical trade-offs between JVM and native mode. This post captures the key questions and answers from that discussion, lightly edited for readability.&lt;/p&gt;&#10;&lt;p&gt;If you have been following this blog series, note that the third installment on building your own stack with Quarkus is coming next. Consider this a bonus entry that distills the podcast conversation into a format you can read, reference, and share.&lt;/p&gt;</description></item><item><title>Your TLS Stack Is Lying to You About Zero-Copy</title><link>https://foojay.io/today/your-tls-stack-is-lying-about-zero-copy/</link><pubDate>Wed, 10 Jun 2026 12:00:28 +0000</pubDate><guid>https://foojay.io/today/your-tls-stack-is-lying-about-zero-copy/</guid><description>&lt;h2 id="the-no-waste-compute-constraint"&gt;The &amp;ldquo;No Waste Compute&amp;rdquo; Constraint&lt;/h2&gt;&#10;&lt;p&gt;When I started designing the Exeris Kernel, I set one non-negotiable rule very early: no waste compute. That rule sounds like a performance slogan until it starts killing otherwise normal design decisions.&lt;/p&gt;&#10;&lt;p&gt;I had already banned &lt;code&gt;ThreadLocal&lt;/code&gt;, moved context propagation to Scoped Values, and pushed more of the runtime into explicit off-heap ownership. The idea was simple: if the hot path is supposed to stay outside GC pressure, then memory shape and lifetime cannot be treated as incidental details.&lt;/p&gt;</description></item><item><title>How to Develop AI Agents Using BoxLang AI: A Practical Guide</title><link>https://foojay.io/today/how-to-develop-ai-agents-using-boxlang-ai-a-practical-guide/</link><pubDate>Tue, 12 May 2026 12:52:39 +0000</pubDate><guid>https://foojay.io/today/how-to-develop-ai-agents-using-boxlang-ai-a-practical-guide/</guid><description>&lt;p&gt;&lt;img src="https://foojay.io/today/how-to-develop-ai-agents-using-boxlang-ai-a-practical-guide/boxlang-ai-v3-1-700x467.jpg" alt="" width="700" height="467" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;AI agents are transforming how we build software. Unlike traditional chatbots that just answer questions, agents can reason about what tools they need, decide when to use them, chain multiple actions together, and remember what happened earlier in a conversation.&lt;/p&gt;&#10;&lt;p&gt;In this tutorial, I&amp;rsquo;ll show you how to build a real-world AI agent using &lt;a href="https://ai.boxlang.io/" title="BoxLang AI" target="_blank" rel="noopener noreferrer"&gt;BoxLang AI&lt;/a&gt; — the official AI framework for the BoxLang JVM language. We&amp;rsquo;ll build &lt;strong&gt;SupportBot&lt;/strong&gt;, an e-commerce customer support agent that can look up orders, check inventory, issue refunds, and answer questions grounded in your knowledge base.&lt;/p&gt;</description></item><item><title>Explore Spring AI SDK – Amazon Bedrock AgentCore – Part 3</title><link>https://foojay.io/today/explore-spring-ai-sdk-amazon-bedrock-agentcore-part-3/</link><pubDate>Sun, 10 May 2026 09:09:00 +0000</pubDate><guid>https://foojay.io/today/explore-spring-ai-sdk-amazon-bedrock-agentcore-part-3/</guid><description>&lt;p&gt;In &lt;a href="https://foojay.io/today/spring-ai-amazon-bedrock-sdk-guide/"&gt;Part 1&lt;/a&gt; and &lt;a href="https://foojay.io/today/explore-spring-ai-sdk-amazon-bedrock-agentcore-part-2/"&gt;Part 2&lt;/a&gt;, we explored the Spring AI SDK and Amazon Bedrock AgentCore features, including the agentcore runtime starter and integration of agentcore memory. In this article, we will explore the integration of AgentCore built-in tools, including the Browser and Code Interpreter features.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Repository containing the companion code for the tutorial. &lt;a href="https://github.com/bsmahi/simple-spring-boot-agent" target="_blank" rel="noopener noreferrer"&gt;Go to GitHub&lt;/a&gt;.&lt;/strong&gt;&#10;&lt;img src="https://foojay.io/today/explore-spring-ai-sdk-amazon-bedrock-agentcore-part-3/AgentcoreBrowser.jpg" alt="AgentCore Built-In Tool Browser" width="1024" height="576" loading="lazy" decoding="async"&gt; Built-In Tool Browser&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;&lt;em&gt;The use case I am trying to build here is for the given URL; it navigates the entire website and retrieves the content and gives key points and the summary of the page using &lt;strong&gt;the AgentCore Browser&lt;/strong&gt; tool.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>BoxLang AI Deep Dive — Part 7 of 7: MCP — The Protocol That Connects Everything</title><link>https://foojay.io/today/boxlang-ai-deep-dive-part-7-of-7-mcp-the-protocol-that-connects-everything/</link><pubDate>Thu, 07 May 2026 21:51:08 +0000</pubDate><guid>https://foojay.io/today/boxlang-ai-deep-dive-part-7-of-7-mcp-the-protocol-that-connects-everything/</guid><description>&lt;p&gt;&lt;img src="https://foojay.io/today/boxlang-ai-deep-dive-part-7-of-7-mcp-the-protocol-that-connects-everything/bxai-series-cover-07-700x368.png" alt="" width="700" height="368" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;BoxLang AI 3.0 Series · Part 7 of 7&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;The AI ecosystem has a tool problem. Every framework has its own way of defining tools, every agent has its own way of calling them, and every integration requires custom code on both sides. An agent built in Python can&amp;rsquo;t easily use tools built in Java. An MCP server written for Claude Desktop can&amp;rsquo;t easily be consumed by a BoxLang agent without a custom adapter.&lt;/p&gt;</description></item><item><title>UCanAccess: The Modern Pure-Java Bridge to Microsoft Access</title><link>https://foojay.io/today/ucanaccess-java-ms-access-jdbc-guide/</link><pubDate>Wed, 06 May 2026 08:44:00 +0000</pubDate><guid>https://foojay.io/today/ucanaccess-java-ms-access-jdbc-guide/</guid><description>&lt;p&gt;Microsoft Access databases are everywhere. Decades of &lt;code&gt;.mdb&lt;/code&gt; and &lt;code&gt;.accdb&lt;/code&gt; files silently power spreadsheets, small business applications, and legacy data stores across organizations of all sizes. Yet for Java developers, connecting to these files has historically meant wrestling with native Windows libraries, ODBC bridges, and platform-specific hacks.&lt;/p&gt;&#10;&lt;figure class="aligncenter size-full is-resized"&gt;&#10; &lt;img src="https://foojay.io/today/ucanaccess-java-ms-access-jdbc-guide/ucanaccess-logo.svg" alt="UCanAccess Logo" style="width:320px" loading="lazy" class="is-zoomable"&gt;&lt;/figure&gt;&#10;&#10;&lt;p&gt;UCanAccess puts an end to that. It is an open-source, pure-Java JDBC driver that lets you read and write Microsoft Access databases (&lt;code&gt;.mdb&lt;/code&gt; and &lt;code&gt;.accdb&lt;/code&gt;) just like any other SQL database. No native drivers, no Windows dependency, no friction.&lt;/p&gt;</description></item><item><title>BoxLang AI Deep Dive — Part 6 of 7: Memory Systems &amp; RAG — Building AI That Remembers</title><link>https://foojay.io/today/boxlang-ai-deep-dive-part-6-of-7-memory-systems-rag-building-ai-that-remembers/</link><pubDate>Tue, 05 May 2026 15:10:15 +0000</pubDate><guid>https://foojay.io/today/boxlang-ai-deep-dive-part-6-of-7-memory-systems-rag-building-ai-that-remembers/</guid><description>&lt;p&gt;&lt;img src="https://foojay.io/today/boxlang-ai-deep-dive-part-6-of-7-memory-systems-rag-building-ai-that-remembers/bxai-series-cover-06-700x368.png" alt="" width="700" height="368" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;BoxLang AI 3.0 Series · Part 6 of 7&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;A chatbot with no memory isn&amp;rsquo;t a conversation — it&amp;rsquo;s a series of isolated queries. Every message starts from scratch. The user has to re-explain who they are, what they&amp;rsquo;re working on, and what was just said. It&amp;rsquo;s exhausting, and it signals that the AI isn&amp;rsquo;t really listening.&lt;/p&gt;&#10;&lt;p&gt;Memory is what separates a useful AI application from a toy. BoxLang AI ships with one of the most comprehensive memory systems in any AI framework — 20+ memory types across two major categories, vector embedding support for semantic retrieval, 30+ document loaders for RAG pipelines, and a per-call identity routing system that makes multi-tenant applications safe by default.&lt;/p&gt;</description></item><item><title>BoxLang AI Deep Dive — Part 5 of 7: One API, 17 Providers — The Provider Architecture Deep Dive</title><link>https://foojay.io/today/boxlang-ai-deep-dive-part-5-of-7-one-api-17-providers-the-provider-architecture-deep-dive/</link><pubDate>Wed, 29 Apr 2026 16:38:08 +0000</pubDate><guid>https://foojay.io/today/boxlang-ai-deep-dive-part-5-of-7-one-api-17-providers-the-provider-architecture-deep-dive/</guid><description>&lt;p&gt;&lt;img src="https://foojay.io/today/boxlang-ai-deep-dive-part-5-of-7-one-api-17-providers-the-provider-architecture-deep-dive/bxai-series-cover-05-700x368.png" alt="" width="700" height="368" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;BoxLang AI 3.0 Series · Part 5 of 7&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Vendor lock-in is the silent killer of AI projects. You pick OpenAI, build everything against the OpenAI API, and then GPT-5 launches at three times the price. Or a competitor launches a model that&amp;rsquo;s faster for your use case. Or you need to self-host for compliance. Or your client is on AWS and wants Bedrock.&lt;/p&gt;&#10;&lt;p&gt;Every time the answer to &amp;ldquo;can we switch providers?&amp;rdquo; is &amp;ldquo;it would take months,&amp;rdquo; something went wrong architecturally.&lt;/p&gt;</description></item><item><title>BoxLang AI Deep Dive — Part 2 of 7: Building a Production-Grade AI Tool Ecosystem</title><link>https://foojay.io/today/boxlang-ai-deep-dive-part-2-of-7-building-a-production-grade-ai-tool-ecosystem/</link><pubDate>Thu, 16 Apr 2026 09:27:15 +0000</pubDate><guid>https://foojay.io/today/boxlang-ai-deep-dive-part-2-of-7-building-a-production-grade-ai-tool-ecosystem/</guid><description>&lt;p&gt;&lt;img src="https://foojay.io/today/boxlang-ai-deep-dive-part-2-of-7-building-a-production-grade-ai-tool-ecosystem/bxai-series-cover-02-700x368.png" alt="" width="700" height="368" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;BoxLang AI 3.0 Series · Part 2 of 7&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Function calling is where most AI frameworks look deceptively simple on the surface and turn into a mess underneath. You define a tool, pass it to the LLM, and when the LLM calls it — who handles the lifecycle? Who fires observability events? Who serializes the result? Who resolves the tool by name when the only thing you have is a string?&lt;/p&gt;</description></item><item><title>BoxLang AI Deep Dive — Part 1 of 7: The Skills Revolution</title><link>https://foojay.io/today/boxlang-ai-deep-dive-part-1-of-7-the-skills-revolution/</link><pubDate>Tue, 14 Apr 2026 11:50:53 +0000</pubDate><guid>https://foojay.io/today/boxlang-ai-deep-dive-part-1-of-7-the-skills-revolution/</guid><description>&lt;p&gt;&lt;img src="https://foojay.io/today/boxlang-ai-deep-dive-part-1-of-7-the-skills-revolution/bxai-series-cover-01-700x368.png" alt="" width="700" height="368" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;This article is part of our 7-part deep dive on building production-ready AI systems with BoxLang.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;BoxLang AI 3.0 Series · Part 1 of 7&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Every AI framework eventually hits the same wall: your system prompts start drifting. Agent A has a slightly different version of the SQL rules than Agent B. The tone policy on your support bot is three weeks behind the tone policy on your documentation bot. Someone copy-pasted the wrong version. Nobody noticed.&lt;/p&gt;</description></item><item><title>JC-AI Newsletter #15</title><link>https://foojay.io/today/jc-ai-newsletter-15/</link><pubDate>Fri, 20 Mar 2026 07:56:01 +0000</pubDate><guid>https://foojay.io/today/jc-ai-newsletter-15/</guid><description>&lt;p&gt;Over the past two weeks, the field of artificial intelligence has continued its remarkable pace of advancement. As AI becomes increasingly woven into the fabric of daily life, shaping how we work, communicate, and make decisions, it is both timely and valuable to step back and understand the broader trajectory of this technology. Whether the developments around us feel promising or challenging, one truth remains clear: AI is not simply leaving. It is here to stay, and understanding its evolution is essential from many perspectives.&lt;/p&gt;</description></item><item><title>Language Learning Flashcard System - Part 1</title><link>https://foojay.io/today/language-learning-flashcard-system-part-1/</link><pubDate>Tue, 17 Mar 2026 16:39:58 +0000</pubDate><guid>https://foojay.io/today/language-learning-flashcard-system-part-1/</guid><description>&lt;p&gt;My native language is Spanish. I&amp;rsquo;ve been learning (and butchering) English my whole life. But at some point, I felt confident with English and wanted to learn Japanese. Big mistake. This is a totally different beast: three writing systems (Hiragana ひらがな, Katakana カタカナ and Kanji 漢字), a completely different grammar, no relation whatsoever with European languages… I needed help. And tools to learn. And one of them is Space Repetition System based apps.&lt;/p&gt;</description></item><item><title>JC-AI Newsletter #14</title><link>https://foojay.io/today/jc-ai-newsletter-14/</link><pubDate>Tue, 03 Mar 2026 15:11:53 +0000</pubDate><guid>https://foojay.io/today/jc-ai-newsletter-14/</guid><description>&lt;p&gt;&lt;strong&gt;Two&lt;/strong&gt; weeks have passed and a lot have been happening on the field of artificial-intelligence.&lt;/p&gt;&#10;&lt;p&gt;Two weeks have passed and a lot has been silently yet visibly happening in the field of artificial intelligence. This newsletter brings interesting developments, including Dario Amodei&amp;rsquo;s (Anthropic) view on the progress achieved in the LLM field and his response to the utilization of these models for specific kinds of military purposes, as well as OpenAI&amp;rsquo;s response to it. Aside from the fact that development may follow more sigmoids instead of exponential progress, it is important to have awareness of utilization across branches. Does prompting and clarifying the goal influence agent responses, and if so, how? How far are we from reliable robotics applications? How much bias is introduced when clinical data is being analyzed?&lt;/p&gt;</description></item><item><title>Personal Branding Tips for Java Developers</title><link>https://foojay.io/today/watch-the-recording-diy-technical-marketing-for-java-developers/</link><pubDate>Thu, 26 Feb 2026 10:28:58 +0000</pubDate><guid>https://foojay.io/today/watch-the-recording-diy-technical-marketing-for-java-developers/</guid><description>&lt;p&gt;The software development industry is more competitive than ever. Being a strong technical expert is essential, but on its own it is often not enough to grow your career or open new opportunities.&lt;/p&gt;&#10;&lt;p&gt;In this short, practical talk&lt;em&gt;DIY Technical Marketing, Real World Tips For Building A Successful Developer Brand&lt;/em&gt; , delivered at &lt;a href="https://www.jfokus.se/" title="Jfokus 2026 conference" target="_blank" rel="noopener noreferrer"&gt;Jfokus 2026 conference&lt;/a&gt;, Payara Community Manager Dominika Tasarz-Sochacka explores why personal branding matters for developers and how even small, intentional actions can make a real difference over time.&lt;/p&gt;</description></item><item><title>From “Crypto AI” to general AI: Do AI agents dream of electric langoustines?</title><link>https://foojay.io/today/from-crypto-ai-to-general-ai-do-ai-agents-dream-of-electric-langoustines/</link><pubDate>Mon, 23 Feb 2026 18:11:54 +0000</pubDate><guid>https://foojay.io/today/from-crypto-ai-to-general-ai-do-ai-agents-dream-of-electric-langoustines/</guid><description>&lt;h2 id="x402-erc-8004-a2a-and-the-next-wave-of-ai-commerce-do-ai-agents-dream-of-electric-langoustines"&gt;&lt;strong&gt;x402, ERC-8004, A2A, and The Next Wave of AI Commerce: Do AI Agents Dream of Electric Langoustines?&lt;/strong&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;em&gt;&lt;strong&gt;A Blade Runner riff for a world where the lobster ships paid endpoints while humans still argue about the roadmap.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&#10;&lt;h2 id="the-shift-that-matters-for-agent-commerce---from-crypto-ai-to-general-ai"&gt;The shift that matters for agent commerce - From &amp;ldquo;Crypto AI&amp;rdquo; to general AI&lt;/h2&gt;&#10;&lt;p&gt;Today, you can search the web all day and never see an invoice.&lt;/p&gt;&#10;&lt;p&gt;That happens because you are not the paying client.&lt;/p&gt;</description></item><item><title>Unikernel: Profiling and Troubleshooting JVM on Nanos Unikernel</title><link>https://foojay.io/today/unikernel-profiling-and-troubleshooting-jvm-on-nanos-unikernel/</link><pubDate>Wed, 11 Feb 2026 13:50:41 +0000</pubDate><guid>https://foojay.io/today/unikernel-profiling-and-troubleshooting-jvm-on-nanos-unikernel/</guid><description>&lt;h3 id="profiling-a-java-application-running-inside-an-unikernel-with-jprofiler"&gt;Profiling a Java Application Running Inside an Unikernel with JProfiler&lt;/h3&gt;&#10;&lt;p&gt;Unikernels are often associated with minimalism and tight resource control.&lt;/p&gt;&#10;&lt;p&gt;But can we profile a Java application running inside a unikernel using a standard JVM profiler?&lt;/p&gt;&#10;&lt;p&gt;The answer is yes.&lt;/p&gt;&#10;&lt;p&gt;In this guide, we will walk step by step through profiling a Quarkus&lt;/p&gt;&#10;&lt;p&gt;application running inside a Nanos unikernel using &lt;strong&gt;JProfiler&lt;/strong&gt; and&lt;br&gt;&#10;&lt;strong&gt;IBM Semeru JRE 25 (OpenJ9)&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;No special hacks. Just standard JVM tooling.&lt;/p&gt;</description></item></channel></rss>