Home‎ > ‎Adapters‎ > ‎ADB Adapter‎ > ‎Notes‎ > ‎

Differences between ADB Adapter and JDBC Pallet

Issue

ADB Adapter

JDBC Pallet

Data Load

Can handle High to Mid load

The data load will be on the adapter archive instance running on the admin

Use for Mid to Low data

The data load will be on the process archive

Rollback

Cannot implement roll-back mechanism just like JDBC transaction group

JDBC palettes handles rollback much better way

Developed on

C/C++

Hence need System DSN/ODBC

Java

Hence need JDBC

ODBC or JDBC

JDBC for Configuration

ODBC for Deployment

JDBC only

When to use

You will use an adapter when your goal is to make publish/subscribe or request/reply service.  ADB can be configured to watch for CRUD operations in a table and publish those out to the bus (either RV or JMS).  It can also listen to the bus and perform CRUD operations when those events are detected.

JDBC is used when you are in the middle of a BW flow (straight through processing) and need to do a DB operation.  Probably the most common operation is the select to read data to augment your message or verification.

 

It is possible to implement anything ADB does with BW and the JDBC pallet but it is simpler and cleaner to use ADB what it is for.

Drive

Event Driven

Demand Driven

 

 

 


Issue

ADB Adapter

JDBC Pallet

Data Load

Can handle High to Mid load

The data load will be on the adapter archive instance running on the admin

Use for Mid to Low data

The data load will be on the process archive

Rollback

Cannot implement roll-back mechanism just like JDBC transaction group

JDBC palettes handles rollback much better way

Developed on

C/C++

Hence need System DSN/ODBC

Java

Hence need JDBC

ODBC or JDBC

JDBC for Configuration

ODBC for Deployment

JDBC only

When to use

You will use an adapter when your goal is to make publish/subscribe or request/reply service.  ADB can be configured to watch for CRUD operations in a table and publish those out to the bus (either RV or JMS).  It can also listen to the bus and perform CRUD operations when those events are detected.

JDBC is used when you are in the middle of a BW flow (straight through processing) and need to do a DB operation.  Probably the most common operation is the select to read data to augment your message or verification.

 

It is possible to implement anything ADB does with BW and the JDBC pallet but it is simpler and cleaner to use ADB what it is for.

Drive

Event Driven

Demand Driven

 

 

 


•   ADB is more suitable for instances where you have a lot of processing

•   ADB is more suitable for instances where you want that a particular action on a DB Table triggers a BW process.

•   ADB adapter is best for publishing from database.

•   For simple inserts and updates ADB subscriber is best.

•   In case of insert or update to database then check if you have complex JDBC inserts, transaction management and other dynamic queries then JDBC activities are best.

•   JDBC is more suitable for running dynamic code where in runtime you can execute statements with different values depending on process execution

Comments