Abstract: Provided is a process of validating data to be stored in a graph database, the process including: obtaining a first node to be stored in a graph database, the first node having a relationship to a second node corresponding to an edge; obtaining a node type of the first node having a respective node-type schema; forming a polymorphic schema, based on the node-type schema, specifying criteria to qualify as a valid instance of the node type; validating the first node with the polymorphic schema; and in response to validating the first node, storing the first node and the edge in the graph database.

Abstract: Provided is a process, including: obtaining a first application-program interface (API) response from a first software-as-a-service (SaaS) application API, the first API response being arranged according to a first data-serialization format; retrieving a first connector schema from memory based on a mapping in memory of the first connector schema to the first SaaS application API, wherein the first connector schema comprises a plurality of rules by which API responses from the first SaaS API are processed to form nodes or edges of a graph data structure; applying the rules of the first connector schema to at least part of the first API response from the first SaaS application API to form a plurality of nodes and a plurality of edges of the graph data structure; and updating the graph data structure in memory to include the plurality of nodes and the plurality of edges.

Abstract: Provided is a process of validating data to be stored in a graph database, the process including: obtaining a first node to be stored in a graph database, the first node having a relationship to a second node corresponding to an edge; obtaining a node type of the first node having a respective node-type schema; forming a polymorphic schema, based on the node-type schema, specifying criteria to qualify as a valid instance of the node type; validating the first node with the polymorphic schema; and in response to validating the first node, storing the first node and the edge in the graph database.

Abstract: Provided is a process of servicing a dynamic application program interface request that accommodates different contexts of different requests corresponding to different graph database schemas, the process including: receiving a first application program interface (API) request having a first context; selecting a first type of node in a graph database; obtaining a first schema and a second schema corresponding to the first type of node and the first context; determining that the first schema is partially overridden by the second schema; translating the first API request into a query language of the graph database based on both the first schema and overriding portions of the second schema; and submitting the translated graph database request to the graph database.