In my previous post, I referred to exciting new features in the upcoming DB21c JDBC drivers and the availability of the bits by early January. Here we are, past mid-January, so what are those so-called exciting things?
The new features can be grouped under the following categories: support for popular Java frameworks, performance and scalability, support for Cloud native applications, diagnosability and tracing.
In this blog post, I will only give a bullet list; if you are interested in a specific feature please read my technical brief titled “ What’s in DB21c for Java Developers”.
The Oracle JDBC drivers from the 184.108.40.206 release are now available on Maven Central. See the Developers Guide for Oracle JDBC on Maven Central for the details on how to pull the artifacts. In general we recommend to always use the latest driver bits as these include the fixes for known issues.
We’ve fixed an issues introduced in the 220.127.116.11 BOM; more specifically, we missed adding <type>pom</type> to the coordinates of the flavor POMs (a.k.a. “pre-established dependencies”). If you are not pulling the pre-defined set of artifacts using the BOM approach, you need not be concerned about this issue.
In my previous blog post, I’ve indeed mentioned that the support for GraalVM Native Image is coming soon. The JDBC driver from the Oracle database 21c release has it and we will be posting the bits very soon (already available with the Cloud-only release of Oracle Database 21c).
With respect to the Oracle R2DBC driver, it is a separate, open source driver and we are going through the red tape before posting the first drop on GitHub. …
The core Oracle JDBC drivers jar i.e., ojdbc8.jar can be used in isolation. However, depending on the use cases, such as connection pooling, high availability, connectivity to database cloud services, NLS, and so on, additional jars are required. Figuring out which artifacts are needed for such-and-such use case can be mind boggling.
In the previous packaging of our drivers on Maven Central we’ve pre-established dependencies between the artifacts required for the most common use cases. Java developers familiar with Maven have been excluding the un-wanted artifacts. …
Firing up new Serverless containers — a.k.a. cold start — takes from one to several seconds (time varies per platform); to eliminate such cost/latency, Serverless frameworks keep already started containers warm for a period of time (duration varies per provider).
Serverless functions might make database access. Although less costly than starting new Serverless container, database connection creation and tear down may cost tens or even hundreds of milliseconds depending on your DBMS environment. This problem is exacerbated with Serverless functions that are are short-lived and cannot afford such cost on every call. …
Updated to add the newly released 18.104.22.168.
Not just the latest release, all supported releases of the Oracle JDBC drivers including 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206 and 220.127.116.11 are now available on Maven Central. From now on, Maven Central becomes indeed a distribution center for the Oracle JDBC drivers and companion jars.
Beyond the JDBC drivers, we want to consolidate all Oracle database artifacts on Maven Central under the same umbrella com.oracle.database. The artifacts have been dispatched under their specific focus i.e., JDBC, XML, security, high-availability (ha), NLS, observability, SODA (coming soon), AQJMS (coming soon) and so on.
Clearly stated, here is a description of the new group ids of the JDBC drivers and companion…
Yes, you asked for it, and with some delay (better late than ..), we did it!
Maven Central becomes a distribution center for the Oracle JDBC drivers.
We started with the latest release 18.104.22.168 but will soon add previous and supported releases.
Update: please see this post for the latest releases and coordinates.
The Oracle JDBC drivers come with companion jars; what are these and what are the Maven artifacts and their ids?
The Oracle Autonomous Transaction Processing Dedicated (ATP-D) is a database Cloud service which allows implementing a private database Cloud service running on dedicated Exadata Infrastructure within the Oracle Public Cloud. The goal of this blog article is to help you, Java developer or architect, build and deploy fast, scalable, and reliable Java applications with ATP-D, using plain Java, Java Servlets, or Java Microservices with WebLogic, Helidon, WebSphere, Liberty, Tomcat, WildFly (JBoss), Spring, and so on.
I’ll walk you through: (i) the prerequisites and Java connectivity to ATP-D; (ii) zero downtime for Java applications with ATP-D; (iii) and finally, the performance and scalability of Java applications with ATP-D. …
A re-edition of my recent blog post
There is an abundant literature on Java performance (books, articles, blogs, websites, and so on); a Google search returns more than 5 millions hits. To name a few, the Effective Java programming language guide, Java Performance the definitive guide, Java performance tuning newsletter and its associated website.
This blog post revisits the known best practices for speeding up and scaling database operations for Java applications then discusses new mechanisms such as database proxies, and the Asynchronous Database Access (ADBA) proposal.
Optimizing database operations for Java applications includes: speeding up database connectivity, speeding up SQL statements processing, optimizing network traffic, and in-place processing. …