Systems and methods for coordinating the deployment of components to defined user groups
Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.
1. A system comprising:
one or more processors; and
a memory storing instructions that, when executed by the one or more processors, cause the system to:
generate a first stack or a first stack portion to deploy a first application component;
generate a second stack or a second stack portion to deploy a second application component, wherein the first application component has a first stability level or a first confidence level different from a second stability level or a second confidence level of the second application component;
coordinate a deployment of the first application component based on the first stack or the first stack portion and the second application component based on the second stack or the second stack portion;
receive an indication that a new application component satisfies a dependency corresponding to the first stack or the first stack portion, or the second stack or the second stack portion;
in response to receiving the indication, update the first stack or the first stack portion, or the second stack or the second stack portion based on the new application component, wherein the updating of the first stack or the first stack portion, or the second stack or the second stack portion, is based on the first stability level or the first confidence level, or the second stability level or the second confidence level;
in response to updating the first stack or the first stack portion, or the second stack or the second stack portion, update the deployment of the first application component or the second application component and
separately render a first front end component corresponding to the first application component and a second front end component corresponding to the second application component based on the deployment.
2. The system of claim 1 , wherein the instructions further cause the system to:
receive a modification to a first parameter associated with or indicative of the first stability level, or the first confidence level;
modify the first stack or the first stack portion based on the modification to the first parameter; and
render the first front end component based on the modified first stack or the modified first stack portion.
3. The system of claim 1 , wherein the rendering of the first front end component is based on derived information from one or more backend components.
4. The system of claim 1 , wherein the first application component and the second application component comprise static files.
5. The system of claim 1 , wherein the first application component and the second application component each comprise any two selected from a group consisting of: a user interface component, a library, and a program.
6. The system of claim 1 , wherein the generating of the first stack is based on a map of dependencies among the application component, a dependent application component, and a backend component.
7. The system of claim 1 , wherein the first stability level or the first confidence level is indicative of a different development stage compared to the second stability level or the second confidence level.
8. The system of claim 1 , wherein the instructions that, when executed by the one or more processors, cause the system to:
receive an indication of a change in a parameter of the first application component or the second application component, the parameter being indicative of the first stability level, first confidence level, second stability level, or the second confidence level; and
in response to receiving the indication of the change, modify the first stack or the first stack portion, or the second stack or the second stack portion, wherein the modifying comprises:
removing the first application component from the first stack or the first stack portion and replacing the first application component with a new first application component, or removing the second application component from the second stack or the second stack portion and replacing the second application component with a new second application component.
9. A method being implemented by a computing system having one or more processors and a storage media storing machine-readable instructions that, when executed by the one or more processors, cause the computer system to perform the method, the method comprising:
generating a first stack or a first stack portion to deploy a first application component;
generating a second stack or a second stack portion to deploy a second application component, wherein the first application component has a first stability level or a first confidence level different from a second stability level or a second confidence level of the second application component;
coordinating a deployment of the first application component based on the first stack or the first stack portion and the second application component based on the second stack or the second stack portion;
receiving an indication that a new application component satisfies a dependency corresponding to the first stack or the first stack portion, or the second stack or the second stack portion;
in response to receiving the indication, updating the first stack or the first stack portion, or the second stack or the second stack portion based on the new application component, wherein the updating of the first stack or the first stack portion, or the second stack or the second stack portion, is based on the first stability level or the first confidence level, or the second stability level or the second confidence level;
in response to updating the first stack or the first stack portion, or the second stack or the second stack portion, updating the deployment of the first application component or the second application component; and
separately rendering a first front end component corresponding to the first application component and a second front end component corresponding to the second application component based on the deployment.
10. The method of claim 9 , further comprising:
receiving a modification to a first parameter associated with or indicative of the first stability level, or the first confidence level;
modifying the first stack or the first stack portion based on the modification to the first parameter; and
rendering the first front end component based on the modified first stack or the modified first stack portion.
11. The method of claim 9 , wherein the rendering of the first front end component is based on derived information from one or more backend components.
12. The method of claim 9 , wherein the first application component and the second application component comprise static files.
13. The method of claim 9 , wherein the first application component and the second application component each comprise any two selected from a group consisting of: a user interface component, a library, and a program.
14. The method of claim 9 , wherein the generating of the first stack is based on a map of dependencies among the application component, a dependent application component, and a backend component.
15. The method of claim 9 , wherein the first stability level or the first confidence level is indicative of a different development stage compared to the second stability level or the second confidence level.
16. A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors to perform:
generating a first stack or a first stack portion to deploy a first application component;
generating a second stack or a second stack portion to deploy a second application component, wherein the first application component has a first stability level or a first confidence level different from a second stability level or a second confidence level of the second application component;
coordinating a deployment of the first application component based on the first stack or the first stack portion and the second application component based on the second stack or the second stack portion;
receiving an indication that a new application component satisfies a dependency corresponding to the first stack or the first stack portion, or the second stack or the second stack portion;
in response to receiving the indication, updating the first stack or the first stack portion, or the second stack or the second stack portion based on the new application component, wherein the updating of the first stack or the first stack portion, or the second stack or the second stack portion, is based on the first stability level or the first confidence level, or the second stability level or the second confidence level;
in response to updating the first stack or the first stack portion, or the second stack or the second stack portion, updating the deployment of the first application component or the second application component; and
separately rendering a first front end component corresponding to the first application component and a second front end component corresponding to the second application component based on the deployment.
17. The non-transitory computer readable medium of claim 16 , wherein the instructions further cause the one or more processors to perform:
receiving a modification to a first parameter associated with or indicative of the first stability level, or the first confidence level;
modifying the first stack or the first stack portion based on the modification to the first parameter; and
rendering the first front end component based on the modified first stack or the modified first stack portion.
18. The non-transitory computer readable medium of claim 16 , wherein the rendering of the first front end component is based on derived information from one or more backend components.