Embedded Database versus External RDBMS
When you install Integration Server or Microservices Container, the installer asks whether you want to write data to an external RDBMS or an embedded database. You must use an external RDBMS if you are going to:
Cluster server instances.
Install in a production environment with high transaction volumes or large datasets.
Need a database that is scalable, visible, and highly reliable, and that has robust management and recovery tools.
Write document history or cross-referencing data.
Have services log their input pipelines, or post user-defined progress messages.
Use triggers for joins.
Use pub.storage for high-volume storage.
In the case of
Integration Server:
Write Process Audit Log and
Process Engine data for business processes.
Use Mediator or
Monitor.
In the case of
Integration Server or
Microservices Container: Use Business Rules.
If none of the above apply, and your database demands are low, your needs might be met by using the embedded database. For example, in the case of Integration Server or Microservices Container, you can use the embedded database as a runtime for adapters, eStandards Modules, or Deployer. You should use the embedded database with an Integration Server that is an Enterprise Gateway.
