Overview of this article
- The scope of this article consists of infrastructure sequence diagrams between the Tulip platform components with respect to creating and loading records of Tulip Tables in a Tulip app.
- Audience:
- Tulip solution developers
- I.T. engineers
- The purpose of this article is to inform the audience of their Tulip solution's dependencies on:
- reliable connectivity to Tulip cloud infrastructure
- performant and reliable local network infrastructure
- reliability and performance of connected systems
- Tulip-Internal Latency - As a back-of-the-napkin approximation, assume each instance of 'Tulip-Internal Latency' is approximately 100 milliseconds.
Tulip App trigger loading a Tulip Table Record Placeholder

Tulip App trigger creating a Tulip Table record
Optimal - sequential trigger actions for 'Table Record / Create' & 'Data Manipulation / Store'

Non-Optimal - trigger actions for 'Table Record / Create' & 'Data Manipulation / Store' are disrupted

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 solved a similar topic!
