Granted Patent B2

US 12,321,736 · App. 18/584,591 · Granted Jun 3, 2025

Inventors: Manuj Bawa (Clarksburg, MD); John S. Combs (Fallston, MD)

Assignee: JPMORGAN CHASE BANK, N.A.

G06F8/60G06F8/20G06F8/71

Abstract

Claims (56)

1. An electronic device, comprising:

a memory storing an infrastructure seeding engine; and

a computer processor;

wherein, when executed by the computer processor, the infrastructure seeding engine causes the computer processor to:

receive a plurality of extensible application patterns;

publish the extensible application patterns to an application pattern catalog;

receive an instantiate request comprising a selection of one of the plurality of extensible application patterns and a blueprint, wherein the blueprint identifies a deployment technology;

generate metadata for the selected extensible application pattern and the selected blueprint;

generate a configuration for the metadata;

create execution isolations for deployments based on the metadata, wherein the execution isolations comprise a Layer-1 execution scope that identifies network tables, network routing, network isolations, subnets, VLANs, and/or foundational firewall ports for the selected extensible application pattern and a Layer-2 execution scope that comprises infrastructure code the selected extensible application pattern and/or the blueprint;

apply security at the Layer-1 execution scope and the Layer-2 execution scope;

generate source code for the selected extensible application pattern;

create and link the source code for the selected extensible application pattern to a continuous integration/continuous development pipeline; and

deploy the source code and an application artifacts infrastructure based on the Layer-1 execution scope and the Layer-2 execution scope, wherein the deployment achieves an immutable infrastructure.

2. The electronic device of claim 1 , wherein the extensible application patterns comprise an operating system extensible application pattern, and/or a platform extensible application pattern.

3. The electronic device of claim 1 , wherein the metadata comprises execution isolations, inheritances between execution isolations, and/or scopes of configuration parameters between isolation contexts.

4. The electronic device of claim 1 , wherein the metadata identifies a type of application, a geo-location for the application and/or the blueprint, a legal jurisdiction for the application and/or the blueprint, or a data classification check for the application.

5. The electronic device of claim 1 , wherein the code for the selected extensible application pattern is inherited from the published extensible application pattern.

6. The electronic device of claim 1 , wherein the infrastructure seeding engine further causes the computer processor to receive approval for the selected extensible application pattern.

7. A computer-implemented method for deploying federated infrastructure as code, comprising:

receiving, by an infrastructure seeding engine executed by a computer processor, a plurality of extensible application patterns;

publishing, by the infrastructure seeding engine, the extensible application patterns to an application pattern catalog;

receiving, by the infrastructure seeding engine, an instantiate request comprising a selection of one of the plurality of extensible application patterns and a blueprint, wherein the blueprint identifies a deployment technology;

generating, by the infrastructure seeding engine, metadata for the selected extensible application pattern and the selected blueprint;

generating, by the infrastructure seeding engine, a configuration for the metadata;

creating, by the infrastructure seeding engine, execution isolations for deployments based on the metadata, wherein the execution isolations comprise a Layer-1 execution scope that identifies network tables, network routing, network isolations, subnets, VLANs, and/or foundational firewall ports for the selected extensible application pattern and a Layer-2 execution scope that comprises infrastructure code the selected extensible application pattern and/or the blueprint;

applying, by the infrastructure seeding engine, security at the Layer-1 execution scope and the Layer-2 execution scope;

generating, by the infrastructure seeding engine, source code for the selected extensible application pattern;

creating and linking, by the infrastructure seeding engine, the source code for the selected extensible application pattern to a continuous integration/continuous development pipeline; and

deploying, by the infrastructure seeding engine, the source code and an application artifacts infrastructure based on the Layer-1 execution scope and the Laver-2 execution scope, wherein the deployment achieves an immutable infrastructure.

8. The method of claim 7 , wherein the extensible application patterns comprise an operating system extensible application pattern, and/or a platform extensible application pattern.

9. The method of claim 7 , wherein the metadata comprises execution isolations, inheritances between execution isolations, and/or scopes of configuration parameters between isolation contexts.

10. The method of claim 7 , wherein the metadata identifies a type of application, a geo-location for the application and/or the blueprint, a legal jurisdiction for the application and/or the blueprint, or a data classification check for the application.

11. The method of claim 7 , wherein the code for the selected extensible application pattern is inherited from the published extensible application pattern.

12. The method of claim 7 , further comprising: receiving, by the infrastructure seeding engine, approval for the selected extensible application pattern.

13. A system comprising:

a database storing a plurality of extensible application patterns;

an application pattern catalog storing the plurality of extensible application patterns;

a metadata linking store that stores metadata;

a configuration store that stores configuration data;

a security policy store that stores security policies applicable to the plurality of extensible application patterns;

a source code repository that stores source code; and

an electronic device comprising a computer processor and a memory storing an infrastructure seeding engine that, when executed by the computer processor, engine causes the computer processor to:

receive a selection of one of the plurality of extensible application patterns and a blueprint, wherein the blueprint identifies a deployment technology;

generate a configuration for the metadata;

generate metadata for the selected extensible application pattern and the selected blueprint and store the metadata in the metadata store;

create execution isolations for deployments based on the metadata, wherein the execution isolations comprise a Layer-1 execution scope that identifies network tables, network routing, network isolations, subnets, VLANs, and/or foundational firewall ports for the selected extensible application pattern and a Layer-2 execution scope that comprises infrastructure code the selected extensible application pattern and/or the blueprint;

apply security at the Layer-1 execution scope and the Layer-2 execution scope from the security policy store;

generate source code for the selected extensible application pattern and store the source code in the source code repository;

create and link the source code for the selected extensible application pattern to a continuous integration/continuous deployment pipeline; and

deploy the source code and an application artifacts infrastructure based on the Layer-1 execution scope and the Layer-2 execution scope, wherein the deployment achieves an immutable infrastructure.

14. The system of claim 13 , wherein the extensible application patterns comprise an operating system extensible application pattern, and/or a platform extensible application pattern.

15. The system of claim 13 , wherein the metadata comprises execution isolations, inheritances between execution isolations, and/or scopes of configuration parameters between isolation contexts.

16. The system of claim 13 , wherein the metadata identifies a type of application, a geo-location for the application and/or blueprint, a legal jurisdiction for the application and/or the blueprint, or a data classification check for the application.

17. The system of claim 13 , wherein the code for the selected extensible application pattern is inherited from the selected extensible application pattern.

18. The system of claim 13 , wherein the infrastructure seeding engine further causes the computer processor to receive approval for the selected extensible application pattern.

Assignments (1)

Continuity (3)

References Cited (15)