Granted Patent B2

US 12,314,704 · App. 18/369,827 · Granted May 27, 2025

Inventors: William Hickman (Brooklyn, NY); Mark Elliot (London, GB)

Assignee: Palantir Technologies Inc.

G06F8/65G06F9/451

Abstract

Claims (55)

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, wherein the first application component and the first stack or the first stack portion has a first stability level or a first confidence level;

coordinate a deployment of the first application component based on the first stack or the first stack portion;

receive a first indication that the first application component is validated;

in response to receiving the first indication, incorporate the first application component into a second stack or a second stack portion, wherein the second stack or the second stack portion has a second stability level or a second confidence level distinct from the first stability level or the first confidence level;

in response to incorporating the first application component into a second stack or a second stack portion, update a deployment of the second stack or the second stack portion;

receive a second indication that the first application component has increased a stability level or a confidence level beyond a threshold corresponding to a third stability level or a third confidence level;

in response to receiving the second indication, selectively retain the first application component in the second stack or the second stack portion;

if the first application component is not retained in the second stack or the second stack portion, incorporate the first application component into the third stack or the third stack portion;

update a deployment of the second stack or the second stack portion; and

render a front end component corresponding to the second stack or the second stack portion.

2. The system of claim 1 , wherein the first stability level or the first confidence level is associated with a lower stability level or a lower confidence level compared to the second stability level or the second confidence level, and the first indication is associated with the first application component having increased a stability level or a confidence level beyond a threshold corresponding to the second stability level or the second confidence level.

3. The system of claim 1 , wherein the instructions further cause the system to:

in response to receiving the first indication, remove the first application component from the first stack or the first stack portion; and

the removing of the first application component from the first stack or the first stack portion comprises updating a previous mapping among any dependent application components of the first application component.

4. The system of claim 1 , wherein the deployment of the second stack or the second stack portion is from a common server as the deployment of the first stack or the first stack portion.

5. The system of claim 1 , wherein the first application component comprises 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 updating the deployment of the second stack or the second stack portion comprises updating a map of dependencies among the first application component, a dependent application component, and a backend component.

7. 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, wherein the first application component and the first stack or the first stack portion has a first stability level or a first confidence level;

coordinating a deployment of the first application component based on the first stack or the first stack portion;

receiving a first indication that the first application component is validated;

in response to receiving the indication, incorporating the first application component into a second stack or a second stack portion, wherein the second stack or the second stack portion has a second stability level or a second confidence level distinct from the first stability level or the first confidence level;

in response to incorporating the first application component into a second stack or a second stack portion, updating a deployment of the second stack or the second stack portion;

receiving a second indication that the first application component has increased a stability level or a confidence level beyond a threshold corresponding to a third stability level or a third confidence level;

in response to receiving the second indication, selectively retaining the first application component in the second stack or the second stack portion;

if the first application component is not retained in the second stack or the second stack portion, incorporating the first application component into the third stack or the third stack portion;

updating a deployment of the first stack or first stack portion, or the second stack or the second stack portion; and

rendering a front end component corresponding to the second stack or the second stack portion.

8. The method of claim 7 , wherein the first stability level or the first confidence level is associated with a lower stability level or a lower confidence level compared to the second stability level or the second confidence level, and the first indication is associated with the first application component having increased a stability level or a confidence level beyond a threshold corresponding to the second stability level or the second confidence level.

9. The method of claim 7 , further comprising:

in response to receiving the first indication, removing the first application component from the first stack or the first stack portion; and

the removing of the first application component from the first stack or the first stack portion comprises updating a previous mapping among any dependent application components of the first application component.

10. The method of claim 7 , wherein the deployment of the second stack or the second stack portion is from a common server as the deployment of the first stack or the first stack portion.

11. The method of claim 7 , wherein the first application component comprises any two selected from a group consisting of: a user interface component, a library, and a program.

12. The method of claim 7 , wherein the updating the deployment of the second stack or the second stack portion comprises updating a map of dependencies among the first application component, a dependent application component, and a backend component.

13. A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors of a computing system to perform:

generating a first stack or a first stack portion to deploy a first application component, wherein the first application component and the first stack or the first stack portion has a first stability level or a first confidence level;

coordinating a deployment of the first application component based on the first stack or the first stack portion;

receiving a first indication that the first application component is validated;

in response to receiving the indication, incorporating the first application component into a second stack or a second stack portion, wherein the second stack or the second stack portion has a second stability level or a second confidence level distinct from the first stability level or the first confidence level;

in response to incorporating the first application component into a second stack or a second stack portion, updating a deployment of the second stack or the second stack portion;

receiving a second indication that the first application component has increased a stability level or a confidence level beyond a threshold corresponding to a third stability level or a third confidence level;

in response to receiving the second indication, selectively retaining the first application component in the second stack or the second stack portion;

if the first application component is not retained in the second stack or the second stack portion, incorporating the first application component into the third stack or the third stack portion;

updating a deployment of the second stack or the second stack portion; and

rendering a front end component corresponding to the second stack or the second stack portion.

14. The non-transitory computer readable medium of claim 13 , wherein the first stability level or the first confidence level is associated with a lower stability level or a lower confidence level compared to the second stability level or the second confidence level, and the first indication is associated with the first application component having increased a stability level or a confidence level beyond a threshold corresponding to the second stability level or the second confidence level.

15. The non-transitory computer readable medium of claim 13 , wherein the instructions that, when executed, cause one or more processors of a computing system to perform:

in response to receiving the first indication, removing the first application component from the first stack or the first stack portion; and

the removing of the first application component from the first stack or the first stack portion comprises updating a previous mapping among any dependent application components of the first application component.

16. The non-transitory computer readable medium of claim 13 , wherein the deployment of the second stack or the second stack portion is from a common server as the deployment of the first stack or the first stack portion.

17. The non-transitory computer readable medium of claim 13 , wherein the updating the deployment of the second stack or the second stack portion comprises updating a map of dependencies among the first application component, a dependent application component, and a backend component.

Assignments (1)

Continuity (6)

References Cited (144)