Pages

▼
Showing posts with label jpa. Show all posts
Showing posts with label jpa. Show all posts
Tuesday, May 28, 2013

Batch Writing, and Dynamic vs Parametrized SQL, how well does your database perform?

›
One of the most effective database optimizations is batch writing. Batch writing is supported by most modern databases and part of the JDBC...
4 comments:
Thursday, March 7, 2013

But what if I'm not querying by id? (database and cache indexes)

›
Most data models define a sequence generated numeric primary key. This is the most efficient key to use as it is a single efficient guarant...
6 comments:
Thursday, January 3, 2013

Got Cache? improve data access by 97,322%

›
Caching is the most valuable optimization one can make in software development. Making something run faster is nice, but it can never beat ...
1 comment:
Tuesday, November 13, 2012

EclipseLink 15x faster than other JPA providers

›
I'm sorry to disappoint those of you looking to see some canned benchmark showing how EclipseLink dominates over all competitors in perf...
4 comments:
Tuesday, May 15, 2012

JPQL vs SQL, why not have both

›
One of the most common questions I see on JPA, is users wanting to know how to write some specific SQL query as a JPQL query. Some of the t...
13 comments:
Monday, April 23, 2012

Objects vs Data, and Filtering a JOIN FETCH

›
JPA deals with objects, and SQL deals with rows. Some developers love JPA because it allows them to use objects in an object-oriented fashi...
1 comment:
Monday, April 2, 2012

EclipseLink JPA supports MongoDB

›
EclipseLink 2.4 will support JPA access to NoSQL databases. This support is already part of the EclipseLink development trunk and can be tri...
4 comments:
Thursday, June 9, 2011

How to improve JPA performance by 1,825%

›
The Java Persistence API (JPA) provides a rich persistence architecture. JPA hides much of the low level dull-drum of database access, free...
35 comments: