This guide outlines best practices for using Tulip Connectors that scale efficiently in production environments.
Limits on Connectors
| Question | Answer |
|---|---|
| Is there a limit on number of Connectors? | No. |
| Is there a limit on number of Connector Functions on a Connector? | No. |
| What are the limits on the payload size for a request and a response? | The maximum payload size depends on the type of Connector Host used: - Cloud Connector Host Default: 20 MB (Configurable) - On-Premise Connector Host Default: 50 MB (Configurable) - Edge Device Connector Host: 50 MB (Configurable) |
| For a SQL Connector, is there a limit on the number of records returned by a query? | The limit of number of rows returned on a SQL Connector Function is a result of the maximum payload size for the Connector Host used. |
Timeouts on Connectors
| Parameter | Description | Default Timeout |
|---|---|---|
| Connector Timeout | Controls how many seconds the Connector Host will wait before timing out a Connector Function (either HTTP or SQL) or connection by throwing a timeout error. | 20 Seconds (Configurable) |
| Connectors OAuth 2.0 Timeout | Controls how long the Tulip platform will wait when authenticating with OAuth 2.0 before throwing a timeout error | 30 Seconds (Configurable) |
Further Reading
How can users extend this logic, what other content should users read next?
Did you find what you were looking for?
You can also head to community.tulip.co to post your question or see if others have faced a similar question!
.gif)