Modular Network Architecture with Precreated Microservice Security Groups
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The 'chicken and egg' problem arises in modular network architecture when trying to specify relationships using security groups, as not every microservice is deployed in every environment, making it difficult to define communication rules.
Innovation Solution
Each microservice security group is created regardless of whether the corresponding microservice is deployed, resulting in empty security groups with no rules. Upon deployment, microservices add appropriate ingress and egress rules, ensuring that communication is only established when both parties match their rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If security groups are created only for deployed microservices, then the system avoids creating empty security groups, but it becomes impossible to define communication rules for microservices that may be deployed in different environments
Solution Approach 1:
The patent creates security groups for all microservices in advance, before deployment to specific environments. This preliminary creation allows the system to pre-define potential communication relationships without knowing which microservices will actually be deployed. The security groups are created with placeholder configurations, and the actual communication rules are added later when microservices are deployed and their relationships are established.
2Reliability
If all security groups are deployed to all environments, then communication rules can be consistently defined, but unnecessary security groups and rules are created in environments where specific microservices are not deployed
Solution Approach 1:
The patent implements dynamic security group rule management where communication rules are added to security groups based on the actual deployment state of microservices in each environment. When a microservice is deployed, the system dynamically adds the appropriate ingress and egress rules to its security group. When microservices are removed or not deployed, their security groups remain but without active communication rules, avoiding the creation of unnecessary rules while maintaining the ability to quickly enable communication when needed.
3Ease of manufacture
If security groups wait for microservice deployment before creation, then no empty security groups are created, but the 'chicken and egg' problem prevents defining communication rules between microservices that need to communicate
Solution Approach 1:
The patent creates security groups in advance as placeholder structures before microservices are deployed. This preliminary creation of security group frameworks allows the system to have the structural foundation ready, and then populate the actual communication rules later when microservice relationships are known, solving the chicken and egg problem of needing to define rules between services that don't exist yet.
Data Source
AI summary
Devices, systems, methods, and non-transitory computer-readable media for modular network architecture. In one embodiment, a server includes a memory and an electronic processor. The memory stores cloud infrastructure definitions, the cloud infrastructure definitions including a plurality of microservices and security groups that define communication between each of the plurality of microservices. The electronic processor is configured to deploy a first virtual private cloud including a first portion of the plurality of microservices and all of the security groups, deploy a second virtual private cloud including a second portion of the plurality of microservices and the all of the security groups, and deploy a third virtual private cloud including a third portion of the plurality of microservices and the all of the security groups.