<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Functional Programming on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/functional-programming/</link><description>Recent content in Functional Programming on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 13 Jan 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/functional-programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Elasticsearch Java SDK: No Magic, Just Solid Design Choices</title><link>https://javapro-en.svenruppert.com/elasticsearch-java-sdk-no-magic-just-solid-design-choices/</link><pubDate>Tue, 13 Jan 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/elasticsearch-java-sdk-no-magic-just-solid-design-choices/</guid><description>&lt;p&gt;Java&amp;rsquo;s API ecosystem is massive, but quality is not granted for free, and not necessarily widespread. Building a good API is not trivial, and focus is required. You need balanced abstractions, keep the threading model sane, and provide developers a satisfying experience.&lt;/p&gt;
&lt;p&gt;The Elasticsearch Java SDK caught my attention because it actually gets this stuff right. I dug into the design decisions that make it work, and the overall approach is worth understanding, even if there are trade-offs to consider.&lt;/p&gt;</description></item></channel></rss>