Sizing SAP Integration Hub in SAP S/4HANA Cloud Public Edition
Use this information to estimate the resources that SAP Integration Hub needs in your SAP S/4HANA Cloud Public Edition tenant.
Add-on footprint
The add-on consists of approximately 15 MB of delivered objects in the namespaces
/NEP/ and /NEPTUNE/. This size is essentially constant across releases and does
not depend on how you use the add-on. The add-on does not extend any SAP tables.
Persisted data
Beyond the fixed footprint, the persisted data volume depends entirely on your usage. Two factors determine it:
-
Number and complexity of your APIs. Each API definition and its operations are stored in the tenant as configuration data. The volume per API is small and grows linearly with the number of APIs.
-
Logging. Log records are the only part of the data footprint that grows over time in normal operation.
No representative size can be given for a single API definition or log record, because both depend on how you define and use your APIs. Estimate your volume from the number of APIs you plan to deploy, the expected request volume, and the log retention period you choose.
Logging and data growth
Logging is optional and switched off after installation. The add-on persists no log data in the tenant until you enable logging.
When logging is enabled, each API call can produce a log record. Log volume therefore grows with request volume, not with the size of the add-on.
There is currently no housekeeping or automatic deletion of log data. If you enable logging, plan for the growth of log data and delete it according to your own retention policy. Where request volumes are high, enable logging selectively, for example during development and troubleshooting, and use a retention period that meets your audit requirements.
Data transmitted and received
The volume of data transmitted and received depends on the payloads of the APIs you build and on how often they are called. The add-on adds no material overhead to a request beyond the processing of the API framework. Size network and platform capacity from your measured API payloads and expected call volumes.
Performance
Neptune Software has performance-tested the add-on, including SQL trace analysis,
and created table indexes where they improve access times. Quality assurance includes
ABAP Unit tests, automated end-to-end tests, and scheduled ATC runs with the check
variant ABAP_CLOUD_DEVELOPMENT_DEFAULT.
The runtime performance of your APIs depends mainly on your data provider classes. Keep API operations focused, return only the fields that the consuming application needs, and avoid unbounded result sets in list operations.