US 12,373,220 B2Granted

Unified automation of application development

AssigneeAmazon Technologies, Inc.

InventorsMike Paul Spertus, Timothy Simon Bell

Life of this patent

Estimating the term…

Loading patent…

Abstract

Unified automation of application development and delivery is provided. An automation pipeline execution coordinator may define a pipeline specification that includes actions to be performed, a triggering event definition and specification for determining execution context. The coordinator may concurrently detect triggering events for multiple pipelines matching the pipeline specification, and responsive to the detecting, determine execution contexts for the pipelines. The coordinator may then execute the multiple pipelines, where execution may proceed independently for pipelines with differing execution contexts. For pipelines sharing an execution context, execution of various actions of the respective pipelines may be coordinated. Execution context may be determined according to the specification for determining execution context, which may include an overridable default specification that determines context by locations of source data related to the triggering event. Pipeline specifications may be defined using pipeline specification templates and input from users obtained via various user interfaces.

Claims20

Dependent claims

A system, comprising:

one or more processors;
and
a memory storing program instructions that, when executed on the one or more processors, implement a pipeline execution coordinator configured to:
obtain a pipeline specification comprising an action and a triggering event definition, wherein the triggering event definition further comprises a data source definition and a trigger action detected on a data source stored in a location identified by the data source definition;
detect respective triggering events, including a first triggering event and a second triggering event, to cause execution of respective actions of two pipeline executions managed by the pipeline execution coordinator, wherein the first triggering event and the second triggering event match the pipeline specification, and wherein the second triggering event occurs subsequent to the first triggering event;
and
responsive to the detecting, concurrently automate execution of the respective actions of the two pipeline executions, wherein to concurrently automate execution of the respective actions of the two pipeline executions the pipeline execution coordinator is configured to:
identify respective contexts for the two pipeline executions based at least in part on the first triggering event, the second triggering event and the triggering event definition;
select an execution mode of a plurality of different execution modes according to a determination of whether the respective contexts of the two pipeline executions are the same, wherein the selected execution mode is an independent execution mode if the respective contexts are not the same, and wherein the selected execution mode is a coordinated execution mode if the respective contexts of the two pipeline executions are determined to be the same;
and
cause execution of the respective actions of the two pipeline executions according to the selected execution mode, wherein the independent execution mode causes the pipeline execution coordinator to independently execute the respective actions of the two pipeline executions;
and wherein the coordinated execution mode causes the pipeline execution coordinator to coordinate execution of the respective actions of the two pipelines.

9 more elements

A computer-implemented method comprising:

obtaining, from a client, a pipeline specification comprising an action and a triggering event definition;
and
concurrently automating execution of respective actions of two pipeline executions matching the pipeline specification responsive to detecting respective triggering events for the two pipeline executions, wherein concurrently automating execution of the respective actions comprises:
identifying respective contexts for the two pipeline executions based, at least in part, on the respective triggering events and the triggering event definition;
selecting an execution mode of a plurality of different execution modes according to a determination of whether the respective contexts of the two pipeline executions are the same, wherein the selected execution mode is a coordinated execution mode if the respective contexts of the two pipeline executions are determined to be the same, and wherein the selected execution mode is an independent execution mode if the respective contexts are not the same;
and
causing, on behalf of the client, execution of the respective actions of the two pipeline executions according to the selected execution mode, wherein the independent execution mode causes independent execution of the respective actions of the two pipeline executions, and wherein the coordinated execution mode causes coordinated execution of the respective actions of the two pipeline executions.

4 more elements

One or more non-transitory computer-accessible storage media storing program instructions that when executed on or across one or more computing devices cause the one or more computing devices to perform:

obtaining, from a client, a pipeline specification comprising an action and a triggering event definition;
and
concurrently automating execution of respective actions of two pipeline executions matching the pipeline specification responsive to detecting respective triggering events for the two pipeline executions, wherein concurrently automating execution of the respective actions comprises:
identifying respective contexts for the two pipeline executions based at least in part on the respective triggering events and the triggering event definition;
selecting an execution mode of a plurality of different execution modes according to a determination of whether the respective contexts of the two pipeline executions are the same, wherein the selected execution mode is a coordinated execution mode if the respective contexts of the two pipeline executions are determined to be the same, and wherein the selected execution mode is an independent execution mode if the respective contexts are not the same;
and
causing, on behalf of the client, execution of the respective actions of the two pipeline executions according to the selected execution mode, wherein the independent execution mode causes independent execution of the respective actions of the two pipeline executions, and wherein the coordinated execution mode causes coordinated execution of the respective actions of the two pipeline executions.

4 more elements

Dependencies are inferred from the claim text.

Facts

Application: 17/489,571Filed 29 Sep 2021
Published: US 2023/0096376 A130 Mar 2023
Granted: 29 Jul 2025
Term ends: Not estimatedThe source records don’t support an estimate.

Classification13 codes

G06F 9/3828
Bypassing or forwarding of data results, e.g. locally between pipeline stages or within a pipeline stage: with global bypass, e.g. between…
G06F 9/3869
Using instruction pipelines: implementation aspects, e.g. pipeline latches; pipeline synchronisation and clocking
G06F 9/3826
Operand accessing: bypassing or forwarding of data results, e.g. locally between pipeline stages or within a pipeline stage
G06F 9/3836
Concurrent instruction execution, e.g. pipeline or look ahead: instruction issuing, e.g. dynamic instruction scheduling or out of order…