Difference between ODBC / Wire Protocol Drivers and Native Programming

-

Superior performance over competing drivers - DataDirect Connect for ODBC wire protocol drivers offer significant advantages over native ODBC programming.


Advantages of Using ODBC / Wire Protocol Drivers

Disadvantages of Native Programming

Faster than native programming
Using DataDirect wire protocol drivers results in faster application performance than coding to the native database API.

This is possible because DataDirect drivers include many performance features such as network optimization. For example, DataDirect uses compressed data packets that are allowed by the architecture of our drivers, but not by the native interface the database uses. This means significantly fewer packets are transmitted across the wire, resulting in better application performance.

In addition, DataDirect drivers don't use database client libraries to communicate with the database as other drivers do, instead accessing it directly through the database's wire protocol. This eliminates the extra processing that occurs within the performance-inhibiting client libraries.

Coding to the native API of the database actually results in slower application performance than when using the ODBC interface and DataDirect wire protocol ODBC drivers.

More flexible
Developers can write one set of code to the ODBC standard interface to connect to multiple databases.

DataDirect ODBC drivers also offer many interoperability features such as SQL Levelingthat make coding to different databases even easier.

Requires unique, non-portable code in the language of each database the application requires. In a heterogeneous database environment, this can add considerably to development costs.

Improves developer productivity
Developers can write one set of code to the ODBC standard interface to connect to multiple databases. They don't have to learn the intricate details of each database's native interface.

ODBC has other programming advantages:

  • Provides full access to native database functions via ODBC pass-through or escape sequences.
  • Works well on all databases, including Oracle, DB2, Sybase, and MySQL, not just Microsoft SQL Server.
  • Can be used on a variety of platforms: Windows, HP-UX, Linux, AIX and Solaris, as well as a variety of 32 bit and 64 bit chipset architectures

Coding to the native interface of each database is time consuming.

Lowers support costs
Using ODBC makes it easy to extend the database coverage of your application. When you want to support a new database, you just need to get a wire protocol driver for the new database.

And because DataDirect wire protocol drivers don't require database client libraries, you don't have to update these libraries every time there's a change to the database version.

You need different experts for each database you want to code to.

Improves performance and maintenance of existing applications
Switching your application to ODBC/wire protocol drivers can result in a 25-50% performance improvement, and sometimes even more.

It also lowers your support costs because you don't have to update your applications every time there are changes to the underlying databases.

There are few options to improve the performance of a maturing application. Generally this has to come via a technical innovation in software or hardware.

 







Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more