Distributed orchestration architectures, and related systems and methods
AssigneeLiveView Technologies, LLC
InventorsRoy W. Hayward, Steven R. Lindsey
Life of this patent
Estimating the term…
Abstract
Various embodiments relate to event-driven architectures. An event-driven architecture may include an event bus and an orchestrator communicatively coupled to the event bus. The event-driven architecture may also include a number of components communicatively coupled to the event bus. A first component of the number of components is configured to perform a first workflow in response to a first event. Further, the orchestrator is configured to perform a second workflow in response to a second, different event. Associated methods and systems are also disclosed.
Claims25
A system including an event-driven architecture, the system comprising:
- an event bus;
- one or more orchestrators communicatively coupled to the event bus;
- and
- a number of components communicatively coupled to the event bus, wherein, in response to a first event, a first component of the number of components is configured to perform a first workflow of a number of workflows;
- wherein the one or more orchestrators is configured to:
- distribute the first workflow to the first component;
- and
- perform, in response to a second event, a second workflow of the number of workflows.
A system, comprising:
- an event bus;
- a number of components communicatively coupled to the event bus, wherein:
- a first component of the number of the components is a sophisticated component configured to perform a first workflow;
- and
- a second component of the number of components is an unsophisticated component;
- and
- an orchestrator communicatively coupled to the event bus and configured to distribute a workflow to the first component.
A method of operating an event-driven architecture, the method comprising:
- receiving, at a bus of the event-driven architecture, a first message associated with an event;
- responsive to determining that a service of a number of services does not include a workflow for the event:
- generating, via an orchestrator, a second message;
- publishing the second message to the bus;
- and
- receiving, via the service, the second message;
- receiving, via the service, the first message responsive to determining that the service includes the workflow for the event;
- and
- performing an action via the service.
An event-driven architecture, comprising:
- an event bus;
- an orchestrator communicatively coupled to the event bus;
- and
- a number of components communicatively coupled to the event bus;
- wherein responsive to a first event, a first component of the number of components performs a first workflow;
- wherein, responsive to a second, different event, the orchestrator performs a second workflow.
A method of operating an event-driven architecture, the method comprising:
- receiving a number of workflows at an orchestrator of the event-driven architecture;
- determining, for each of a number of components of the event-driven architecture, whether the component is a sophisticated component or an unsophisticated component;
- and
- sending a first workflow of the number of workflows to a first, sophisticated component of the number of components.
Dependencies are inferred from the claim text.