Abstract: A method includes receiving a query directed to a first data model that specifies base data fields. The method includes determining extension bindings for the first data model. A binding specifies an extension to the first data model and specifies one of the base data fields as a node at which the specified extension is added. The extension specifies a non-empty set of data fields. The method includes retrieving base data values according to the base data fields and extension data values according to, for a first binding, the set of data fields. The method includes generating a data object from the base and extension data values according to a second data model. The second data model is based on the first data model extended by adding the data fields from the extension specified by the first binding to the first data model at the specified node.

Abstract: A method includes receiving a query directed to a first data model that specifies base data fields. The method includes determining extension bindings for the first data model. A binding specifies an extension to the first data model and specifies one of the base data fields as a node at which the specified extension is added. The extension specifies a non-empty set of data fields. The method includes retrieving base data values according to the base data fields and extension data values according to, for a first binding, the set of data fields. The method includes generating a data object from the base and extension data values according to a second data model. The second data model is based on the first data model extended by adding the data fields from the extension specified by the first binding to the first data model at the specified node.

Abstract: A query processing method includes receiving a query from a requestor. The query is directed to a first data model specifying multiple base data fields. The method includes determining a set of extension bindings for the first data model based on the query. Each binding specifies an extension to the first data model from a set of model extensions and specifies one of the base data fields of the first data model as a node at which the extension is added. The method includes generating a data object from base data values and extension data values according to an extended data model. The extended data model is defined by the first data model extended by, for each binding of the set, adding data fields from the specified extension to the first data model at the specified node. The method includes returning the data object to the requestor.

Abstract: A query processing method includes receiving a query from a requestor. The query is directed to a first data model specifying multiple base data fields. The method includes determining a set of extension bindings for the first data model based on the query. Each binding specifies an extension to the first data model from a set of model extensions and specifies one of the base data fields of the first data model as a node at which the extension is added. The method includes generating a data object from base data values and extension data values according to an extended data model. The extended data model is defined by the first data model extended by, for each binding of the set, adding data fields from the specified extension to the first data model at the specified node. The method includes returning the data object to the requestor.

Abstract: An event processing system is provided for providing resilient message processing using asynchronous communications. The event processing device includes a processor and a memory. The event processing device is in communication with a publisher microservice and subscriber microservices. The processor is configured to receive an event including a collection of data from the publisher microservice. The processor is also configured to process the event to identify a recipient microservice. The processor is configured to update a queue with a queue entry for each of the at least one recipient microservices for the event. Each queue entry is associated with a priority. The processor is also configured to attempt to transmit the event to each of the at least one recipient microservices until a transmission confirmation message is received. The processor is further configured to update the queue by removing the queue entry for which the transmission confirmation message is received.

Abstract: An event processing system is provided for providing resilient message processing using asynchronous communications. The event processing device includes a processor and a memory. The event processing device is in communication with a publisher microservice and subscriber microservices. The processor is configured to receive an event including a collection of data from the publisher microservice. The processor is also configured to process the event to identify a recipient microservice. The processor is configured to update a queue with a queue entry for each of the at least one recipient microservices for the event. Each queue entry is associated with a priority. The processor is also configured to attempt to transmit the event to each of the at least one recipient microservices until a transmission confirmation message is received. The processor is further configured to update the queue by removing the queue entry for which the transmission confirmation message is received.

Abstract: An event processing system is provided for providing resilient message processing using asynchronous communications. The event processing device includes a processor and a memory. The event processing device is in communication with a publisher microservice and subscriber microservices. The processor is configured to receive an event including a collection of data from the publisher microservice. The processor is also configured to process the event to identify a recipient microservice. The processor is configured to update a queue with a queue entry for each of the at least one recipient microservices for the event. Each queue entry is associated with a priority. The processor is also configured to attempt to transmit the event to each of the at least one recipient microservices until a transmission confirmation message is received. The processor is further configured to update the queue by removing the queue entry for which the transmission confirmation message is received.

Abstract: Business Process Execution Language (BPEL) engines and Enterprise Service Buses (ESBs) often connect to adapters to integrate backend packaged applications with a process flow by invoking web services using Java Connector Architecture (JCA) and Simple Object Access Protocol (SOAP) bindings. The Web Service Description Language (WSDL) files for the web services that interact with the adapters can be introspected to harvest adapter integration and transformation information into a service metadata repository. This permits dependency and impact analysis to extend from services to adapters and transformations.

Abstract: Business Process Execution Language (BPEL) engines and Enterprise Service Buses (ESBs) often connect to adapters to integrate backend packaged applications with a process flow by invoking web services using Java Connector Architecture (JCA) and Simple Object Access Protocol (SOAP) bindings. The Web Service Description Language (WSDL) files for the web services that interact with the adapters can be introspected to harvest adapter integration and transformation information into a service metadata repository. This permits dependency and impact analysis to extend from services to adapters and transformations.