<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Java on Pi Stack</title><link>https://www.pistack.xyz/tags/java/</link><description>Recent content in Java on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/java/index.xml" rel="self" type="application/rss+xml"/><item><title>Drools vs OpenL Tablets vs Easy Rules: Self-Hosted Business Rules Engine Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-21-drools-vs-openl-tablets-vs-easy-rules-self-hosted-business-rules-engine-guide-2026/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-21-drools-vs-openl-tablets-vs-easy-rules-self-hosted-business-rules-engine-guide-2026/</guid><description>&lt;p>Business logic buried inside application code is one of the most common sources of technical debt. When pricing rules, compliance checks, eligibility criteria, or routing decisions are hardcoded, every change requires a full development cycle — code, test, build, deploy.&lt;/p></description></item></channel></rss>