Usage limits

The usage of customer-built services is limited by the licensing, which is based on the number of minutes of usage, number of requests, and storage. If the maximum resource usage is exceeded, a rate limiting switch can be applied, that blocks access to the services for the remaining period.

Build and deployment

  • Max 25 services can be concurrently deployed for each tenant.
  • During the build of the services, outbound communication is restricted. Consequently, all dependencies must be included with the provided source code prior to initiating a build.

Execution

  • Outbound communication is allowed only through API Gateway.
  • The maximum concurrency per service depends on the tenant suffix:
    • **PRD:** 10
    • **Any other suffix (e.g.DEV, TST, AX1):** 5

The maximum concurrency for a tenant is calculated from the number of deployed services and the allowed number of concurrent executions for the tenant type. For example, up to 25 REST services can be deployed concurrently for a tenant, which results in a maximum of 250 concurrent REST executions for a PRD tenant. For a tenant with any other suffix, the maximum concurrent executions for the REST services is 125.

Timeouts

  • **REST API handler:** 25 seconds
  • **Queue, schedule and storage handler:** 10 minutes
  • **Temporary URL:** 15 minutes

REST payload

The payload size for request/response are limited to a total of 6 MB/4.5 MB for text/binary files including headers. **Suggested workaround:** Consider creating a temporary URL for storage of larger files.

Storage

The maximum storage for the BaaS services is included in the total storage for Infor OS. Files and logs are included in the cloud storage count. Cassandra and KeyValue storage is included in the database storage count. Deleted files are included in the storage count for 30 days.

Queue

The maximum size of a queue message is 256 kB. For larger messages, use the temporary storage and include the key name in the message.

Logging

Each log message can contain text only up to 5000 characters, longer messages are truncated to reduce the cost for logging.