Data Separation

Edit online
webMethods API Gateway stores the data in Elasticsearch by default. It includes the core data and analytics data. These two data types are different in the following ways:
Core data Analytics data
Includes APIs and assets that are critical to keep business running. Includes the API analytics data
Requires frequent backup. For example, 15 minutes. Can be backed up in lesser frequent intervals. For example, 24 hours.
Requires lesser storage space than the analytics data. Requires huge storage space.

Hence, if you are managing large transactions volume, it is recommended to save the core data and analytics data separately.

To separate the core data from analytics data, you can configure two Elasticsearch instances and save the core data and analytics data in each Elasticsearch instance as illustrated below in fig.

Data separation
When you save the analytics data in an Elasticsearch instance, the data is not reflected in the webMethods API Gateway Dashboard. You can configure a separate Kibana dashboard for your Elasticsearch destination.

Data Separation Benefits

The main benefit of data separation is that the webMethods API Gateway core data is lesser in size when compared to the analytics data. The data stored in Elasticsearch remains light and
  • Performance of the application improves.
  • Data housekeeping and data backup processes become faster and simpler.