Invantive Cloud Structure

This article provides an overview of the structure of Invantive Cloud. Some elements have been excluded, such as applicable additional controls, filters and firewall settings. These are available only with NDA.

Invantive Cloud is op drie manieren te benaderen:

  1. Cloud: via de web user interface op
  2. Bridge Online: via OData4 queries op
  3. App Online: via eigen web apps op

Alle drie de wijzes kunnen bij dezelfde databasedefinities en datacontainers zoals Twinfield, Simplicate, Yuki, Exact Online. Je kunt op alle drie de manieren ook databases benaderen die meerdere soorten datacontainers bevatten; een eigen web apps kan bijvoorbeeld gegevens lezen in Yuki en schrijven in Vismanet.

Bridge Online

When an OData4 query is received by Invantive Bridge Online, the OData4 query is rewritten into an Invantive SQL statement on the virtual database. The Invantive SQL statement is then executed. The results of the SQL statement are packaged in OData4 response format and returned as a stream of data. The stream-nature allows your OData4 client to start receiving despite not all data yet fetched from the backing platform such as Twinfield or Exact Online.


Invantive Bridge maintains a number of caches that are configurable on a database level:

OData4 Response Cache

The OData4 response cache contains answers on previously OData4 queries. The same answer will be served over and over again during a time frame determined by the value of the field “Bridge Response Cache Maximum Age (sec)” on your database definition. The value is by default 4 hours (14.400 seconds). When the answer is served from the OData4 response cache, the Invantive SQL engine is not used.

Platform Response Cache

The platform response cache of Bridge Online within Invantive Cloud contains answer by the backing platform such as AFAS or Exact Online on previously queries to the platform in their respective desired API protocol. The same answer will be used when the same query is to be sent to the platform by the Invantive SQL engine in composing the answer to the SQL statement generated from your OData4 query. The maximum age can be seen at the value of the field “HTTP Disk Cache Maximum Age (sec)” on your database definition. The value is by default 4 hours (14.400 seconds).

Subscription Constraints

The cache lifetime settings are also dependent on the subscription chosen. The maximum age has no effect when lower than the settings on the subscription. The subscription-specific settings can be found by navigating to “Subscriptions” and then clicking on the product code such as “SUBCMEA02”: