Object-oriented infrastructure-as-code platform (OOIACP)

A system, comprising:

• a computing system, comprising:
• an object-oriented infrastructure-as-code platform(“OOIACP”);
• at least one first processor;
• and
• a first non-transitory computer readable medium communicatively coupled to the at least one first processor, the first non-transitory computer readable medium having stored thereon computer software comprising a first set of instructions that, when executed by the at least one first processor, causes the computing system to:
• receive, from a requesting device, a request to perform a function, wherein the request to perform the function comprises a request to process one or more lifecycle events;
• and
• when the request to process the one or more lifecycle events is received, perform a first set of tasks comprising:
• selecting and scaling across a first plurality of OOIACP instances for processing the one or more lifecycle events;
• and
• causing the selected first plurality of OOIACP instances to process the one or more lifecycle events, each first OOIACP instance among the first plurality of OOIACP instances comprising an infrastructure-as-code (“IAC”) command line that instantiates component infrastructure among a plurality of component infrastructure to process at least one lifecycle event among the one or more lifecycle events concurrently and independently of other OOIACP instances among the first plurality of OOIACP instances, wherein the first plurality of OOIACP instances is located within an environment in which the plurality of component infrastructure is located,
• wherein the request to perform the function comprises a representational state transfer (“REST”) call, the REST call comprising a context_in file containing one or more custom environment variables, wherein the instructions, when executed by the at least one first processor, further causes the computing system to:
• receiving, at each first OOIACP instance, the request to perform the function via an Internet of Components (“IoC”) factory application programming interface (“API”);
• storing, using an IoC factory command line interface (“CLI”) script at each first OOIACP instance, the context_in file in disk storage;
• sourcing, using the IoC factory CLI script, the context_in file within a customized environment within the first OOIACP instance;
• running the IoC factory CLI script in the customized environment, based on the context_in file;
• retrieving a product suite image from a repository based on the context_in file, the product suite image comprising at least one of a directory of IAC files, a set of resources, a set of modules, or a set of libraries;
• executing one or more IAC commands against the product suite image;
• generating component infrastructure, using the IAC commands, based on specifications in the product suite image;
• logging into the generated component infrastructure;
• and
• for each successive layer of the IoC, retrieving one or more product workloads from the repository based on the context_in file;
• and performing lifecycling of the generated component infrastructure by running a create, read/retrieve, update, delete, list and batch(“CRUDLB”) script on the generated component infrastructure based on the context_in file.

A method, comprising:

• receiving, with a computing system and from a requesting device, a request to perform a function, wherein the computing system comprises an object-oriented infrastructure-as-code platform (“OOIACP”), wherein the request to perform the function comprises at least one of a request to process one or more lifecycle events or a request to process one or more workload events;
• when the request to process one or more lifecycle events is received, performing, by the computing system using at least one of a subject-based multicast (“SBM”) system, a distributed business process management system(“DBPMS”) engine platform, or an artificial intelligence for information technology operations (“AIOps”) system, the following:
• selecting and scaling across a first plurality of OOIACP instances for processing the one or more lifecycle events;
• and
• causing the selected first plurality of OOIACP instances to process the one or more lifecycle events, each first OOIACP instance among the first plurality of OOIACP instances comprising an infrastructure-as-code (“IAC”) command line that instantiates component infrastructure among a plurality of component infrastructure to process at least one lifecycle event among the one or more lifecycle events concurrently and independently of other OOIACP instances among the first plurality of OOIACP instances;
• and
• when the request to process one or more workload events is received, performing, by a global load balancer of the computing system, the following:
• selecting and scaling across a second plurality of OOIACP instances for processing the one or more workload events;
• and
• causing the selected second plurality of OOIACP instances to process the one or more workload events, each second OOIACP instance among the second plurality of OOIACP instances instantiating workload resources among a plurality of workload resources to process at least one workload event among the one or more workload events concurrently and independently of other OOIACP instances among the second plurality of OOIACP instances, wherein the first and second plurality of OOIACP instances are located within an environment in which the plurality of component infrastructure and the plurality of workload resources are located,
• wherein the request to perform the function comprises a representational state transfer (“REST”) call, the REST call comprising a context_in file containing one or more custom environment variables, wherein the method further comprises:
• receiving, at each first OOIACP instance, the request to perform the function via an Internet of Components (“IoC”) factory application programming interface (“API”);
• storing, using an IoC factory command line interface (“CLI”) script at each first OOIACP instance, the context_in file in disk storage;
• sourcing, using the IoC factory CLI script, the context_in file within a customized environment within the first OOIACP instance;
• running the IoC factory CLI script in the customized environment, based on the context_in file;
• retrieving a product suite image from a repository based on the context_in file, the product suite image comprising at least one of a directory of IAC files, a set of resources, a s et of modules, or a set of libraries;
• executing one or more IAC commands against the product suite image;
• generating component infrastructure, using the IAC commands, based on specifications in the product suite image;
• logging into the generated component infrastructure;
• and
• for each successive layer of the IoC, retrieving one or more product workloads from the repository based on the context_in file;
• and performing lifecycling of the generated component infrastructure by running a create, read/retrieve, update, delete, list and batch(“CRUDLB”) script on the generated component infrastructure based on the context_in file.