Datasource Types Explained

In Twinnoverse, a datasource is any source of external information that you want to visualize in your 3D scenes. To accommodate different kinds of data streams, the platform supports different methods of data retrieval, primarily categorized as (Only Push for now).

Understanding the difference is key to choosing the right setup for your needs.

Push Datasources #

A Push datasource, also known as an endpoint-based datasource, is a passive listener. It provides a unique, secure URL (the Ingestion URL) and waits for an external system to send data to it.

This is the primary method used in the current version of Twinnoverse.

How It Works:

1. You create an “API Ingest” datasource in Twinnoverse.
2. The system generates a unique Ingestion URL and a secret API Key.
3. You configure your external application, script, or IoT device to send an HTTP POST request to this URL whenever there is new data.
4. The request must include the API Key for authentication.
5. Twinnoverse receives the data, validates it, and updates any linked widgets in real-time.

Characteristics:

• Real-Time: Data appears almost instantly because it is sent the moment it’s generated.
• Offline: Since you push the data to the Datasource you can work with your local data.
• Efficient: Twinnoverse is not constantly asking for updates. It only acts when data arrives.
• You Are in Control: Your external system controls the rate and logic of when data is sent.

Best For:

• IoT sensors that send readings on a schedule or when a value changes.
• Event-driven systems (e.g., sending an update when an order is placed).
• Integrating with low-code platforms like n8n or Make.com that can easily make HTTP requests.
• Any scenario where you can write a script to post data.