Abstract: A method includes identifying a plurality of queries from an application, the plurality of queries associated with an application programming interface (API) and determining an API schema coverage map associated with the plurality of queries. The method further includes generating transformation metadata in view of the API schema coverage map and generating a serverless architecture configuration associated with the application in view of the transformation metadata.

Abstract: A data query for data is received that is associated with a first data node managed by a first executable service and a second data node managed by a second executable service. The data query comprises a subquery that is directed to the second executable service for access to the second data node. From the data query, a selection set is determined. The selection set includes the first data node and the second data node. In view of the selection set, a batch access request is generated to the second executable service that retrieves data for the subquery from the second data node in a single access request.

Abstract: Systems and methods for specifying a stream processing topology via a client-side API without server-side support. A schema may be generated by a client-side application using a query language and transmitted to a stream processor registry, wherein the schema defines a desired data stream. The stream processor registry, acting as a server-side run time corresponding to the query language, may store the schema as metadata. The stream processor registry may generate a stream processing topology based on the metadata to obtain data relevant to the data stream and generate a user-specific topic comprising the data relevant to the data stream. The stream processor registry may filter the data relevant to the data stream based a subscription call by the client to generate a target topic comprising portions of the data relevant to the data stream.

Abstract: A data query for data is received that is associated with a first data node managed by a first executable service and a second data node managed by a second executable service. The data query comprises a subquery that is directed to the second executable service for access to the second data node. From the data query, a selection set is determined. The selection set includes the first data node and the second data node. In view of the selection set, a batch access request is generated to the second executable service that retrieves data for the subquery from the second data node in a single access request.

Abstract: A method includes identifying a plurality of queries from an application, the plurality of queries associated with an application programming interface (API) and determining an API schema coverage map associated with the plurality of queries. The method further includes generating transformation metadata in view of the API schema coverage map and generating a serverless architecture configuration associated with the application in view of the transformation metadata.

Abstract: Systems and methods for specifying a stream processing topology via a client-side API without server-side support. A schema may be generated by a client-side application using a query language and transmitted to a stream processor registry, wherein the schema defines a desired data stream. The stream processor registry, acting as a server-side run time corresponding to the query language, may store the schema as metadata. The stream processor registry may generate a stream processing topology based on the metadata to obtain data relevant to the data stream and generate a user-specific topic comprising the data relevant to the data stream. The stream processor registry may filter the data relevant to the data stream based a subscription call by the client to generate a target topic comprising portions of the data relevant to the data stream.