Templatized Infrastructure Provisioning for Microservice Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Platform teams face challenges in managing hundreds or thousands of microservices with constantly changing infrastructure resources and continuous integration/continuous delivery (CI/CD) configurations, requiring complex coordination and consistent standards, while developers struggle with deploying code using containers and serverless technologies.
Innovation Solution
A managed application deployment service that connects and coordinates tools for infrastructure provisioning, code deployments, monitoring, and updates, using infrastructure templates and translation logic to shield developers from low-level infrastructure details, and provides a centralized view of provisioned resources for consistent management and monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If platform teams manually manage hundreds or thousands of microservices with constantly changing infrastructure resources, then they can provide customized infrastructure for each service, but the complexity of coordination and management increases significantly
Solution Approach 1:
The patent introduces an infrastructure provisioning system as an intermediary between developers and infrastructure resources. This system uses templates to define infrastructure configurations and automatically provisions resources based on these templates, eliminating the need for manual coordination of hundreds of microservices while maintaining adaptability through template customization.
Solution Approach 2:
The patent employs templates with configurable parameters to define infrastructure resources. By changing template parameters rather than manually configuring each resource, the system maintains adaptability for customized infrastructure while significantly reducing management complexity through parameterized automation.
2Adaptability or versatility
If developers directly deploy code using containers and serverless technologies, then they have flexibility in deployment methods, but they must deal with low-level infrastructure details and complexities
Solution Approach 1:
The infrastructure provisioning system acts as an intermediary that developers interact with through simplified templates rather than directly managing container orchestration or serverless configuration details. This maintains deployment flexibility through template choices while hiding infrastructure complexities.
Solution Approach 2:
The patent uses templates as reusable copies of infrastructure configurations. Developers can copy proven infrastructure patterns through templates and modify them as needed, maintaining flexibility while avoiding the need to recreate infrastructure configurations from scratch and reducing exposure to low-level details.
3Adaptability or versatility
If infrastructure resources are constantly changed to meet service requirements, then services can be optimized for specific needs, but consistency and reliability of infrastructure management decrease
Solution Approach 1:
The patent enables service optimization through template parameter changes rather than fundamental infrastructure reconfigurations. This allows services to be optimized for specific needs while maintaining infrastructure consistency through the template framework that ensures valid configurations.
Solution Approach 2:
The system provides feedback mechanisms to ensure infrastructure changes maintain consistency and reliability. By monitoring and validating template parameter changes against defined constraints and best practices, the system allows service optimization while preventing configurations that would compromise infrastructure reliability.
Data Source
AI summary
Features are disclosed for dynamically provisioning an application stack using a set of infrastructure resources. A computing device can receive an infrastructure template from an administrative device. Based on the infrastructure template, the computing device can determine a schema and an infrastructure as code. Using the schema, the computing device can receive a specification file from a developer device or an administrative device. The specification file can be a service specification file or an environment specification file. The computing device can inject the values of the specification file into the infrastructure as code. The computing device can use the injected infrastructure as code to generate and deploy the application stack to the developer device.