Installer 10.7 | Complete Installation and Upgrade Information for Software AG Products | Installing Software AG Products On Premises | Preparing for Database Component Creation | Database Component Descriptions and Installation Requirements | Integration Server or Microservices Runtime Database Components | External RDBMS versus Embedded Database
 
External RDBMS versus Embedded Database
You must use an external RDBMS with Integration Server or Microservices Runtime if you are going to:
*Cluster server instances.
*Install in a production environment with high transaction volumes or large datasets. The definition of "high" and "large" depends on the amount of memory available to your JVM, the speed of your CPU, and the kind of work your application is doing (for example, more processing intensive, or more IO intensive).
*Need a database that is scalable, visible, and highly reliable, and that has robust management and recovery tools.
*Write document history data.
*Have services log their input pipelines.
*Use triggers for joins.
*Use pub.storage for high-volume storage.
*Write Process Audit Log and Process Engine data for business processes.
*Use Business Rules.
*Use Monitor.
If you are not going to do any of the above, and your database demands are low, your needs might be met by using the embedded database. For example, you can use the embedded database when you are using Integration Server or Microservices Runtime as a runtime for adapters, eStandards Modules, API Gateway, or Deployer.