SivaLabs

I got a chance to review the upcoming Cloud Native Spring in Action book by Thomas Vitale and here is my review of the book.

In the Java world, JPA/Hibernate is the most popular and widely used framework. When it comes to the overall performance of a software system, the database persistence layer plays a crucial role. The tricky part with JPA/Hibernate is that it is very easy to get started but very, very hard to master. This is where Vlad Mihalcea’s High-Performance Java Persistence book helps you a lot.

I would like to let you know that I have updated/added the following sections to my SpringBoot: Learn By Example book.

Additions to existing chapters:

• Working with Multiple Databases
• Exposing JPA entities with bi-directional references through RESTful services

I am happy to announce that my new book, SpringBoot: Learn By Example, was published today on Leanpub.

I am glad to announce that my second book, “PrimeFaces Beginner’s Guide,” has been published.

As many of us know, PrimeFaces is the leading JSF component library for JSF-based web applications. This “PrimeFaces Beginner’s Guide” book targets Java developers with a basic knowledge of JSF and jQuery and covers most of the commonly used PrimeFaces components.

The good news is that the “PrimeFaces Beginner’s Guide” book covers the latest PrimeFaces 4.0 version features, such as the Client-Side Validations (CSV) framework, Dialog Framework, Search Expressions, Sticky Component, and many other enhancements as well.

Hurray… My first book, Java Persistence with MyBatis3, is published. I would like to thank Packt Publishers for giving me this opportunity to write about my favorite framework, MyBatis.

For most software applications, data persistence is a key and important aspect. In the Java world, we have many ways of implementing the persistence layer, starting from low-level JDBC to fancy ORM frameworks. JDBC is too low-level an API and requires writing a lot of boilerplate code. On the other hand, we have full-fledged ORM frameworks like JPA (Hibernate, EclipseLink, etc.) which hide the complexity of working with SQL directly by letting developers work with objects and generate SQL based on the RDBMS (Dialect) being used. But each approach has its own set of pros and cons; there is no one-size-fits-all solution. Many large applications are using Hibernate successfully, and many other applications got screwed up by using Hibernate/JPA incorrectly. It is not a problem with JPA/Hibernate; it is simply because JPA/Hibernate may not be the best fit for those applications, or developers don’t understand them properly.