<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JPA on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/jpa/</link><description>Recent content in JPA on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 31 Dec 2025 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/jpa/index.xml" rel="self" type="application/rss+xml"/><item><title>High Speed JPA</title><link>https://javapro-en.svenruppert.com/high-speed-jpa/</link><pubDate>Wed, 31 Dec 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/high-speed-jpa/</guid><description>&lt;p&gt;JPA sometimes carries the stigma of being “too slow for production.” Yet in countless projects, it has quietly powered reliable enterprise systems at scale. The truth is more nuanced: JPA itself is not the bottleneck — but the way we use it can turn convenience into catastrophe. In this article, we’ll explore why green tests can hide critical performance problems, and how a handful of practical techniques can transform JPA from a suspected culprit into a trusted high-speed partner.&lt;/p&gt;</description></item><item><title>Next Generation Caching &amp; In-Memory Searching</title><link>https://javapro-en.svenruppert.com/next-generation-caching-and-in-memory-searching/</link><pubDate>Mon, 28 Jul 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/next-generation-caching-and-in-memory-searching/</guid><description>&lt;h2 id="when-traditional-databases-reach-their-limits"&gt;&lt;strong&gt;When Traditional Databases Reach Their Limits&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Enterprise applications frequently face performance bottlenecks that stem from the underlying persistence layer. Despite decades of database evolution, many core applications still struggle with latency, throughput, and architectural complexity. These issues are particularly evident in systems that depend on complex join operations across multiple tables, need to process unstructured data, or must execute cross-database queries spanning disparate systems to fulfill analytical workflows.&lt;/p&gt;
&lt;p&gt;In such environments, it is common to see a combination of various technologies being deployed in tandem: a traditional relational database, a distributed cache, a NoSQL database, and sometimes a dedicated search server such as Elasticsearch. While each of these systems addresses a specific technical challenge, their co-existence leads to architectural fragmentation, high infrastructure costs, duplicated data models, and increased development and maintenance efforts. Moreover, the overall latency and resource usage often remain suboptimal due to inherent I/O-bound limitations and serialization overheads between systems.&lt;/p&gt;</description></item><item><title>Java and Databases: From SQL to JPA and NoSQL</title><link>https://javapro-en.svenruppert.com/java-and-databases-from-sql-to-jpa-and-nosql/</link><pubDate>Thu, 19 Jun 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-and-databases-from-sql-to-jpa-and-nosql/</guid><description>&lt;p&gt;Over the past 30 years, Java has significantly changed the way applications interact with databases. In the early days, Java applications typically used a client/server model and a three-tier architecture, where SQL statements were often embedded as string literals within the application. These statements were sent to databases through straightforward interfaces such as JDBC.&lt;/p&gt;
&lt;p&gt;As programming paradigms shifted towards Object-Oriented Programming (OOP), Java developers began to integrate business logic more seamlessly into data structures. This move represented a shift from purely database-centric models to application-first designs. This transition enabled data abstraction through application programming interfaces (APIs), allowing SQL database tables and rows to be represented as classes and objects within the application. As a result, data sharing and persistence also evolved, moving from strictly normalized relational tables to document-oriented databases that align more closely with object-oriented structures and specific use cases.&lt;/p&gt;</description></item><item><title>EclipseStore: The Evolution of Java Persistence</title><link>https://javapro-en.svenruppert.com/eclipsestore-the-evolution-of-java-persistence/</link><pubDate>Mon, 12 May 2025 11:24:29 +0000</pubDate><guid>https://javapro-en.svenruppert.com/eclipsestore-the-evolution-of-java-persistence/</guid><description>&lt;p&gt;Database development in Java has always been a challenge, often feeling like a battle against mismatched paradigms. From the start, developers wrestled with complex mappings and performance bottlenecks when integrating Java with databases. EclipseStore, an open-source project under the Eclipse Foundation, was created to change this. Its mission is to deliver a Java-native persistence layer that feels like an integral part of the language, not a workaround for database limitations. By storing Java objects directly, it aims to simplify and accelerate development, aligning persistence with Java’s core strengths.&lt;/p&gt;</description></item><item><title>Optimizing Java Performance: Caching with Core Java Instead of Complex Frameworks</title><link>https://javapro-en.svenruppert.com/optimizing-java-performance-caching-with-core-java-instead-of-complex-frameworks/</link><pubDate>Mon, 05 May 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/optimizing-java-performance-caching-with-core-java-instead-of-complex-frameworks/</guid><description>&lt;p&gt;Slow Java applications are a well-known problem in many projects: delays caused by ORM, complicated caching structures, and overloaded databases slow down performance. At &lt;a href="https://2025.europe.jcon.one/"&gt;JCON EUROPE 2025&lt;/a&gt;, the two-hour workshop “&lt;a href="https://schedule.jcon.one/?selectedSession=797351"&gt;High-Performance Caching with Pure Java: Supercharge Your Sluggy Database Application&lt;/a&gt;” will show how to specifically solve these problems — exclusively with Core Java, without additional frameworks or cloud services.&lt;/p&gt;
&lt;h2 id="hands-on-caching-and-queries-at-maximum-speed"&gt;Hands-on: Caching and Queries at Maximum Speed&lt;/h2&gt;
&lt;p&gt;Participants will learn how to develop a high-performance caching and query layer themselves — lean, memory-efficient, and directly in Java. The goal is to eliminate typical performance bottlenecks in database-based applications and increase system speed many times over.&lt;/p&gt;</description></item></channel></rss>