Artificial Intelligence
AI Agent Authorization: From OAuth Access to Bounded Business Actions
A valid token is only the beginning. Enforce delegated authority, exact approvals and current business policy before an AI agent changes enterprise state.
Best Practices
XRPL Sponsored Fees and Reserves: Designing Onboarding Without an Open-Ended Liability
XRPL sponsorship can simplify onboarding, but reserve commitments need budgets, authorization and a verified exit. A tested policy core shows the boundaries.
Best Practices
XRPL Batch Is Live: Atomic Transactions Need Evidence of Completion
On October 9, 2026, BatchV1_1 became enabled on the XRP Ledger mainnet. For developers, this creates a practical way to group related ledger actions under one explicit execution policy. For software architects, it also creates a new responsibility: distinguish acceptance of the batch from completion of the business operation. The Read more
Best Practices
Spring Modulith and DDD: From Business Boundaries to Reliable Events
A package called orders does not become a bounded context just because its name sounds like the business. And an event called OrderConfirmed does not make an integration reliable just because a listener receives it on your laptop. The interesting direction in Spring Modulith is the connection between these two Read more
Artificial Intelligence
AI Agents and XRPL Payments: Building an Authorization Boundary with Spring AI and xrpl4j
Test an AI payment authorization boundary in Java: tenant-scoped Spring AI tools, immutable approvals, fee caps and unsigned xrpl4j transactions.
Best Practices
Reliable XRPL Payments in Java: Settlement Evidence with xrpl4j
Build a tested Java settlement boundary with xrpl4j: verify delivered value, issuer and final ledger evidence, then commit an idempotent credit and outbox event together.
Best Practices
Spring Framework 7 Resilience: Protect Your Dependencies in the Virtual Thread Era
Test Spring Framework 7 retries and concurrency limits with real proxies and virtual threads. Protect dependencies, avoid retry amplification, and understand timeout boundaries.
Best Practices
Your Telemetry Needs Tests: OpenTelemetry Contracts for Java
The payment provider fails. Your checkout counter keeps rising. The dashboard looks healthy. The trace contains a checkout span, but the payment call sits in another trace. And somewhere in the exception data, a customer email has slipped into your observability platform. The application may have passed its functional tests. Read more
Best Practices
Your Modular Monolith Needs an Architecture Test
A developer needs one more field for an order confirmation. The inventory module already has it, so they import a convenient internal class. The code compiles. The feature works. The boundary on the architecture diagram has just disappeared. That is a practical problem worth solving before splitting an application into Read more
Best Practices
Java 27 Compact Object Headers: Measure the Savings Before You Resize Production
Compact headers are now the default in Java 27. Our tested example shows why smaller headers do not make every object smaller.