JDBC vs. R2DBC vs. Spring JDBC vs. Spring Data JDBC
Last updated: January 8, 2024
Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
Distributed systems often come with complex challenges such as service-to-service communication, state management, asynchronous messaging, security, and more.
Dapr (Distributed Application Runtime) provides a set of APIs and building blocks to address these challenges, abstracting away infrastructure so we can focus on business logic.
In this tutorial, we'll focus on Dapr's pub/sub API for message brokering. Using its Spring Boot integration, we'll simplify the creation of a loosely coupled, portable, and easily testable pub/sub messaging system:
1. Introduction
When it comes to working with databases in Java applications, we’ve various options available. JDBC, R2DBC, Spring JDBC, and Spring Data JDBC are among the most popular frameworks for interacting with databases. Each framework offers unique features and benefits for efficiently handling database operations.
In this quick tutorial, we’ll dive into the world of database connectivity frameworks and explore how each one brings its unique strengths to the table. From traditional JDBC to cutting-edge R2DBC and everything in between, we’ll unravel their inner workings and compare their features side by side to choose the right tool.
2. JDBC
JDBC (Java database connectivity) is the oldest and most widely used standard for accessing databases in Java. It offers a set of interfaces and classes to execute SQL queries, retrieve results, and perform other database operations.
Its strength lies in its ability to efficiently handle simple and complex database operations. Furthermore, it remains a go-to framework because of its widespread acceptance, reliability, and versatility in managing database connections and queries.
One of the limitations of JDBC is that it uses a blocking I/O model, which can cause performance problems if there are a lot of concurrent requests.
3. R2DBC
Unlike JDBC, R2DBC (Reactive Relational Database Connectivity) uses reactive streams and a non-blocking I/O model to handle database operations. This combination of reactivity and non-blocking I/O makes it highly suitable for concurrent systems.
R2DBC can be used in modern reactive programming frameworks such as RxJava and Reactor. It supports both transactional and non-transactional operations.
R2BC is a newer technology. Therefore, not all databases support it. In addition, the available drivers might vary depending on the database we’re using. Moreover, it also has a steep learning curve.
3. Spring JDBC
Spring JDBC is a lightweight abstraction layer on top of JDBC. It simplifies database access by providing a higher-level API and handling many common tasks, such as connection management and exception handling. In addition, it reduces boilerplate code by efficiently managing repetitive tasks by providing parameterized queries and mapping query results to Java objects.
A significant benefit of Spring JDBC is its seamless integration with other Spring components and frameworks.
Because it relies on the blocking IO model of JDBC, it may limit scalability in highly concurrent systems. Moreover, it falls short in terms of the set of features when compared to other frameworks, namely Hibernate.
4. Spring Data JDBC
One more database access tool offered by the Spring ecosystem is Spring Data JDBC. Compared to JDBC and R2DBC, it follows a repository-style approach for database interactions.
Spring Data JDBC is an automatic choice for applications that value simplicity in both domain and code generation. It plays well with domain-driven design and offers support for mapping domain objects to database tables using annotations and conventions. Other than mapping Java objects to database tables, it also provides easy-to-use repository interfaces for common CRUD operations.
Spring Data JDBC is a relatively new framework, and as such, it doesn’t have the same level of maturity as other frameworks. For example, it doesn’t offer much support for complex queries, so we have to write queries ourselves. Additionally, it doesn’t support transactions, which can be a problem in some cases.
5. Comparison
Ultimately, the best choice among JDBC, R2DBC, Spring JDBC, and Spring Data JDBC depends on specific requirements. However, the nature of the application may also play a role in the decision.
The following table can help us to make a decision:
| Feature | JDBC | R2DBC | Spring JDBC | Spring Data JDBC |
|---|---|---|---|---|
| API | Low level | Low level | High level | High level |
| Performance | Good | Excellent | Good | Good |
| Communication | Synchronous | Reactive | Synchronous | Asynchronous |
| Maturity | Mature | Newer | Mature | Newer |
| Features | Fewer features | Few features | More features | More features |
| Ease of use | Easy | Moderate | Easy | Easy |
| Support | Widespread | Growing | Widespread | Growing |
6. Conclusion
In this article, we’ve looked at several database approaches in the Java ecosystem.
For a traditional, synchronous, and widely supported approach, JDBC or Spring JDBC might be the right choice. Similarly, for a reactive application with non-blocking database access, R2DBC could be a good fit. In the last, for simplicity and a higher level of abstraction, Spring Data JDBC might be the ideal option.
By understanding the strengths and weaknesses of each framework, we can make a decision that best suits application needs and helps to build robust, scalable, and maintainable database access code.
