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 to deploy a front end component, the first stack comprising an application component, a dependent application component and a backend component;
generate a second stack to deploy a second front end component, the second stack comprising a second application component, a second dependent application component and one of the backend component or a second backend component;
coordinate a deployment of the front end component based on the first stack and the second front end component based on the second stack;
associate the application component with a first user based on a parameter of the application component;
associate the second application component with a second user based on a second parameter of the second application component; and
in response to the association of the application component with the first user and the second application component with the second user, render the front end to an interface of the first user and the second front end to a second interface of the second user.
2. The system of claim 1 , wherein the second dependent application component is isolated from interacting with the application component, and the dependent application component is isolated from interacting with the second application component.
3. The system of claim 1 , wherein:
the generation of the first stack is based on a map of dependencies among the application component, the dependent application component and the backend component; and
the generation of the second stack is based on a map of second dependencies among the second application component, the second dependent application component and the backend component or the second backend component.
4. The system of claim 1 , wherein the generation of the first stack comprises identifying that the application component, the dependent application component, and the back end component are associated with the first stack based on:
a stability level or a confidence level; and
an access level or an access control of the application component, the dependent application component, and the back end component.
5. The system of claim 1 , wherein the instructions further cause the system to:
update the first stack or the second stack based on an ingestion of a new application component, the updating of the first stack or the second stack comprising determining a time at which to update the first stack or the second stack.
6. The system of claim 1 , wherein the instructions further cause the system to:
update the first stack based on an updated parameter of the application component, the dependent application component, or the back end component; or
update the second stack based on an updated parameter of the second application component, the second dependent application component, or the second back end component.
7. The system of claim 1 , wherein the generation of the second stack occurs subsequent to the generation of the first stack.
8. The system of claim 1 , wherein each of the application component and the second application component comprises a static file, a user interface component, a library, or a program.
9. The system of claim 1 , wherein the rendering of the front end to the interface of the first user precludes rendering of the second front end to the interface of the first user.
10. The system of claim 1 , wherein the application component is implemented in one or more other stacks besides the first stack.
11. 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 to deploy a front end component, the first stack comprising an application component, a dependent application component and a backend component;
generating a second stack to deploy a second front end component, the second stack comprising a second application component, a second dependent application component and one of the backend component or a second backend component;
coordinating a deployment of the front end component based on the first stack and the second front end component based on the second stack;
associating the application component with a first user based on a parameter of the application component;
associating the second application component with a second user based on a second parameter of the second application component; and
in response to the association of the application component with the first user and the second application component with the second user, rendering the front end to an interface of the first user and the second front end to a second interface of the second user.
12. The method of claim 11 , wherein the second dependent application component is isolated from interacting with the application component, and the dependent application component is isolated from interacting with the second application component.
13. The method of claim 11 , wherein:
the generation of the first stack is based on a map of dependencies among the application component, the dependent application component and the backend component; and
the generation of the second stack is based on a map of second dependencies among the second application component, the second dependent application component and the backend component or the second backend component.
14. The method of claim 11 , wherein the generation of the first stack comprises identifying that the application component, the dependent application component, and the back end component are associated with the first stack based on:
a stability level or a confidence level; and
an access level or an access control of the application component, the dependent application component, and the back end component.
15. The method of claim 11 , further comprising:
updating the first stack or the second stack based on an ingestion of a new application component, the updating of the first stack or the second stack comprising determining a time at which to update the first stack or the second stack.
16. The method of claim 11 , further comprising:
updating the first stack based on an updated parameter of the application component, the dependent application component, or the back end component; or
updating the second stack based on an updated parameter of the second application component, the second dependent application component, or the second back end component.
17. The method of claim 11 , wherein the generation of the second stack occurs subsequent to the generation of the first stack.
18. The method of claim 11 , wherein each of the application component and the second application component comprises a static file, a user interface component, a library, or a program.
19. The method of claim 11 , wherein the rendering of the front end to the interface of the first user precludes rendering of the second front end to the interface of the first user.
20. The method of claim 11 , wherein the application component is implemented in one or more other stacks besides the first stack.