Hi, “I think Loom is going to kill reactive programming.” This statement comes from Brian Goetz . Do you know who he is? Brian has been the Java Language Architect at Oracle for 13 years. He is the author of “Java Concurrency in Practice” - a standard work for every Java developer . He was also the one who brought JSR-335 - Lambda Expressions - into the language. What Brian says has substance.
In the world of JVM persistence, Hibernate has a firm place. As one of the most popular frameworks for data persistence, it offers a multitude of possibilities to make developers’ lives easier. One of these possibilities is the Hi/Lo algorithm, a database identifier generation strategy that allows reducing the number of database calls when new entities are persisted. The Challenge of Identifier Generation Before we dive into the Hi/Lo algorithm, let’s briefly look at the challenge of identifier generation in a database.
Hi, Class comments, architecture documentation, method comments, API documentation, inline comments, feature documentation, wireframes, entity-relationship diagrams, use-case diagrams, process documentation, end-user documentation… There are so many things one can document. But what do I really need? Documentation doesn’t write itself. Someone has to take the time. And for it to truly add value, it needs to be well-written, as complete as possible and focused. Not everyone can do that. In large corporations - with thousands of employees - a lot is documented.
Hi, An error in accounting can be costly. Especially in large companies, where there are many transactions, it is easy to overlook one. And when that happens, I might not even notice it. Perhaps the company is doing much better than the books indicate? Or maybe it’s actually unprofitable? Merchants in the 13th century recognized the problem. A system had to be found that would make errors less likely. They invented double-entry bookkeeping.
If you’re dealing with backend development on the JVM, you’ll surely come across the Java Persistence API (JPA). A well-known implementation framework for it is Hibernate. In this article, we’ll show you how you can optimize the performance of your application in Spring Data JPA with caching by preventing the same resources from being fetched multiple times. What is the First-Level-Cache? Spring Data JPA uses Hibernate as the default ORM (Object-Relational Mapping), which provides an inbuilt First-Level-Cache.
Marcus Held