Method and apparatus for hybrid service event
The system provides an event driven system that sits between the enterprise ecosystem and the client system. The system creates a bridge between systems that produce actionable information and systems that consume events related to that information. It coordinates data-change events between those internal microservices for the client, providing a simple, well-typed interface for change events that may drive downstream actions in a consuming service. In one embodiment, the system can intercept those messages, decorate them with client-specific configuration data, and send them to the appropriate downstream client systems, all the while tracking the state of events to provide an auditable window into the system. Events are designed to help an appropriately credentialed and authorized consuming system dynamically call the enterprise's API resources in post-processing by providing relative linking as an out-of-the-box attribute of the event messages.
1. A method of performing operations comprising:
identifying data and events required to perform each process of a plurality of processes, wherein an event is a change to the state of an application and is represented as an Event Object;
using a composition engine for generating a primitive for each process;
receiving a plurality of asynchronous Inbound Event Objects:
defining routing of each Inbound Event Object;
generating an Outbound Event Object by mapping each Inbound Event Object to one or more of the primitives;
adding each Outbound Event Object to a task graph;
providing the data to the task graph and performing an operation on the data using the task graph.
2. The method of claim 1 further including the step of adding metadata to each Outbound Event Object to aid in downstream processing.
3. The method of claim 2 further including the step of combining the task graph with one or more other task graphs.
4. The method of claim 2 wherein a primitive comprises one of the group of S/FTP; Encrypt/Decrypt; Generic HTTP/Consumer; Generic HTTP/Producer; Map; Validator, and Persistence.
5. The method of claim 2 wherein the operation to be performed links one system with one system.
6. The method of claim 2 wherein the operation to be performed links one system with many systems.
7. The method of claim 2 wherein the operation to be performed links many systems with many systems.