Java Survey Results, Part IV - Data Access Tools for SQL

DZone 's Guide to

Java Survey Results, Part IV - Data Access Tools for SQL

The fourth part of David Kiss' Java research. Hibernate, JPA, and JDBC were the clear winners

· Java Zone ·
Free Resource

This post is the fourth one publishing the results of the Java survey I ran recently where I asked developers on tools/frameworks they used in the last 12 months. Respondents had the option to choose from a predefined list of options or select Others and provide any other choice.

Here’s the list of topics covered in the survey:

  1. Languages
  2. Web Frameworks
  3. Application Servers
  4. Data Access Tools for SQL
  5. RDBMS Servers
  6. Big Data
  7. Build Tools
  8. Cloud Provider

This time we’ll be covering tools on the JVM that makes it easy to access data in SQL databases.

Survey Results

Image title

  • JPA – the standard Java Persistence API
  • Hibernate – a pioneer of the Object Relational Mapping (ORM) frameworks in Java
  • JDBC – standard Java API for accessing SQL databases
  • Spring Data – a productivity toolkit on top of JPA, part of the Spring platform
  • Java Object Oriented Querying – an innovative solution for a better integration of Java applications with popular SQL databases
  • GORM – a Grails project, a Groovy-based Object Relational Mapping framework on top ofHibernate
  • MyBatis – Java persistence framework that couples objects with stored procedures or SQL statements using an XML descriptor or annotations
  • Doctrine Project – while the survey was focusing on Java based tools, respondents could select the Other option and provide any tools they wanted. In this case, Doctrine is a PHP framework, it’s the home to several PHP libraries primarily focused on database storage and object mapping
databases, java, sql

Published at DZone with permission of David Kiss , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}