Contents x
API Gateway Data Model and General Interaction Diagram
  • 17 Nov 2023
  • 1 Minute to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF
Contents

API Gateway Data Model and General Interaction Diagram

  • Updated on 17 Nov 2023
  • 1 Minute to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF
Article Summary

API Gateway data model

There are two entities in the API Gateway data model:

  • API (endpoint);
  • Path (resource).

path and ID.png

A single API entity is a collection of paths. When creating an API (Simulator workspace menu->Corezoid) a new Project in Corezoid is created with default Production and Develop Stages.
Each of the created APIs (Stages) gets an ID. An API ID is a unique string which identifies that the API in URLs is a part of FQDN (Fully Qualified Domain Name). For example, in the https://foo.example.com/bar/baz URL, the foo string is the API ID.

APIs in a Corezoid Project

To add new APIs to the default Production and Develop ones, or remove APIs, you need to open the created Corezoid Project and manually create or remove the unneeded Stages in it. After that, click Refresh in the Projects -> Stages menu in Simulator to see the changes.

Path entities (which you can create in Simulator workspace menu->Corezoid->To all APIs->Projects->Stages by clicking the Create path button) store information on target Corezoid processes and call parameters. Any API path is represented by a URL path. In the https://foo.example.com/bar/baz URL, the /bar/baz string is the path.

Paths within an API

Every path-method pair must be unique within its API

This design enables using, for example, different request methods when sending tasks to the same process.

API Gateway interaction diagram

API Gateway Sequence.drawio.png

API Gateway interaction general workflow

The general workflow for API Gateway use can be described as follows:

  1. A user creates a Corezoid Project with default Develop and Production Stages, which are API entities (endpoints) with their own IDs, and path entities (resources) attached to each API. The user then provides an API administrator with the required information, including the target process ID and call parameters.
  2. The API administrator obtains a URL for calling the created path.
  3. A client sends a task to the provided URL.
  4. API Gateway receives the task and proxies it to Corezoid.
  5. If the called path is Synchronous, API Gateway waits for the task processing result from Corezoid;
    If the called path is Asynchronous, API Gateway responds to the client with the 204 status as soon as the task is accepted by Corezoid.
What's Next