Implementation and interpretation of API routing domain-specific language

An API router comprising:

• at least one data processor;
• and
• a memory storing instructions that, when executed by the at least one data processor, cause the API router to:
• define, for each of a plurality of services, one or more routing data objects according to a domain-specific programming language, each including a match expression that is a logical combination of one or more attribute condition statements using one or more Boolean operators,
• wherein evaluation of the match expression produces a single output indicating whether a given API message matches the one or more routing data objects,
• wherein each attribute condition statement is specific to a message attribute and includes a data value and a relational operator by the message attribute is compared to the data value, and wherein the relational operator of each attribute condition statement is one of a set of operators that is specific to a data type of the message attribute;
• perform at least one matching operation between a first API message and a plurality of routing data objects,
• wherein each matching operation for a given one of the plurality of routing data objects includes:
• evaluating, with the message attributes of the first API message, the one or more attribute condition statements of the match expression of the given one of the plurality of routing data objects, and
• determining whether the match expression is logically true according to the logical combination of the one or more attribute condition statements;
• based on performing the at least one matching operation, identify a particular routing data object that matches the first API message based on the match expression of the particular routing data object being logically true with the message attributes of the first API message;
• and
• route the given API message according to one or more policies associated with the particular routing data object.

A platform implemented by a computing system comprising:

• at least one processor;
• and
• at least one memory including instructions that when executed cause the at least one processor to execute:
• a plurality of services;
• and
• an API gateway configured to route API messages to or from the plurality of services, the API gateway configured to:
• store, in the at least one memory, a plurality of routing data objects each associated with one of the plurality of services according to a domain-specific programming language,
• wherein each routing data object includes a match expression that logically combines one or more attribute condition statements using one or more Boolean operators,
• wherein evaluation of the match expression produces a single output indicating whether a given API message matches the one or more routing data objects,
• wherein each attribute condition statement is specific to a message attribute and includes a data value and a relational operator by which the message attribute is compared to the data value, and
• wherein the relational operator of each attribute condition statement is one of a set of operators that is specific to a data type of the message attribute,
• perform at least one matching operation between the given API message and the plurality of routing data objects,
• wherein each matching operation for a given one of the plurality of routing data objects includes:
• evaluating, with the message attributes of the given API message, the one or more attribute condition statements of the match expression of the given one of the plurality of routing data objects, and
• determining whether the match expression is logically true according to the logical combination of the one or more attribute condition statements,
• based on performing the at least one matching operation, identify a particular routing data object that matches the given API message based on the match expression of the particular routing data object being logically true with the message attributes of the given API message,
• route the given API message to or from a particular service according to the particular routing data object.

A router configured to execute instructions for interpreting a domain-specific programming language, the router comprising:

• at least one processor;
• and
• at least one memory including the instructions, wherein the instructions when executed cause the router to interpret aspects of the domain-specific programming language including:
• a set of attributes each indicated by a particular data string and each relating to an aspect of API messages received at the router;
• a set of relational operators that each define a comparison between a given attribute and a given data value, wherein each relational operator is one of a set of operators that is specific to a data type of the given attribute;
• an attribute condition statement composed of an attribute, a relational operator, and a data value against which the attribute is compared according to the relational operator;
• and
• execution of matching operations between a given API message and a plurality of routing data objects,
• wherein each matching operation for a given one of the plurality of routing data objects includes:
• evaluating, with the message attributes of the given API message, the attribute condition statement of a match expression of the given one of the plurality of routing data objects, and
• determining whether the match expression is logically true according to a logical combination of the attribute condition statement,
• based on the execution of matching operations, the router identifies a particular routing data object that matches the given API message based on the match expression of the particular routing data object being logically true with the message attributes of the given API message;
• a set of combinatorial operators each configured to logically combine two attribute condition statements to form a match expression that results in one logical output indicating whether an API message matches a routing data object.