IP Library Granted Patent US 11,681,829
Granted Patent B2
US 11,681,829 · App. 17/493,168 · Granted Jun 20, 2023

Approaches for managing restrictions for middleware applications

Inventors: James Ding (New York, NY); Gonçalo Silva Santos (London, GB); Richard Helzberg (San Geronimo, CA); Thomas Playford (London, GB)
Assignee: Palantir Technologies Inc.
G06F21/629G06F21/604H04L63/101H04L63/105G06F2221/2135G06F2221/2137G06F2221/2141G06F2221/2149
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,681,829
App. No.
17/493,168
Granted
Jun 20, 2023
Kind
B2
Abstract

Systems and methods are provided for determining an access request provided by an application that seeks to interact with one or more backend systems through a computing system. One or more predefined restrictions can be enforced on the application, the computing system, or the one or more backend systems.

Claims (41)

1. A computer-implemented method, comprising:

receiving, by a middleware application system, from a first application and a second application running on a first computing device and a second computing device, respectively, access requests to data stored in a database;

processing, by the middleware application system, the access requests;

determining a schema associated with an entity on which the middleware application system relies in order to retrieve the data stored in the database, wherein the entity comprises an application programming interface (API) or a database table; and

in response to determining the schema, selectively restricting modifications to the schema, wherein the selectively restricting of the modifications to the schema comprises:

determining whether an update to a particular version of a particular software library introduces a breaking change in the entity; and

in response to determining that the update does introduce a breaking change, preventing the update.

2. The computer-implemented method of claim 1 , wherein the determination of a schema comprises:

accessing a dependency matrix indicating sources relied upon by the middleware applications system; and the selectively restricting of modifications to the schema comprises:

preventing modifications to respective schemas associated with the sources.

3. The computer-implemented method of claim 1 , wherein the selectively restricting of modifications to the schema comprises determining whether or not to implement deployments upon the entity and on a new entity based on a predicted likelihood of the deployments interrupting service on the middleware application system.

4. The computer-implemented method of claim 1 , wherein the processing of the access requests comprises segregating, by the middleware application system, subsets of data obtained from the database depending on whether the first application or the second application makes the access requests.

5. The computer-implemented method of claim 1 , wherein the entity comprises a software application or a software library; and the selectively restricting of modifications to the schema comprises preventing a deletion of components of the schema.

6. A system, comprising:

a middleware application system configured to:

receive, from a first application and a second application running on a first computing device and a second computing device, respectively, access requests to data stored in a database;

process the access requests; and

one or more processors in communication with the middleware application system; and

a non-transitory memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform:

receiving an indication regarding an entity on which the middleware application system relies in order to retrieve the data stored in the database, wherein the entity comprises an application programming interface (API) or a database table;

determining a schema associated with the entity; and

in response to determining the schema, selectively restricting modifications to the schema, wherein the selectively restricting of the modifications to the schema comprises:

determining whether an update to a particular version of a particular software library introduces a breaking change in the entity; and

in response to determining that the update does introduce a breaking change, preventing the update.

7. The system of claim 6 , wherein the determination of a schema comprises:

accessing a dependency matrix indicating sources relied upon by the middleware applications system; and the selectively restricting of modifications to the schema comprises:

preventing modifications to respective schemas associated with the sources.

8. The system of claim 6 , wherein the selectively restricting of modifications to the schema comprises determining whether or not to implement deployments upon the entity and on a new entity based on a predicted likelihood of the deployments interrupting service on the middleware application system.

9. The system of claim 6 , wherein the processing of the access requests comprises segregating, by the middleware application system, subsets of data obtained from the database depending on whether the first application or the second application makes the access requests.

10. The system of claim 6 , wherein the entity comprises a software application or a software library; and the selectively restricting of modifications to the schema comprises preventing a deletion of components of the schema.

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

receiving an indication regarding an entity on which the middleware application system relies in order to process an access request, the access request comprising retrieving data stored in a database, wherein the entity comprises an application programming interface (API) or a database table;

determining a schema associated with the entity; and

in response to determining the schema, selectively restricting modifications to the schema, wherein the selectively restricting of the modifications to the schema comprises:

determining whether an update to a particular version of a particular software library introduces a breaking change in the entity; and

in response to determining that the update does introduce a breaking change, preventing the update.

12. The non-transitory computer readable medium of claim 11 , wherein the determination of a schema comprises:

accessing a dependency matrix indicating sources relied upon by the middleware applications system; and the selectively restricting of modifications to the schema comprises:

preventing modifications to respective schemas associated with the sources.

13. The non-transitory computer readable medium of claim 11 , wherein the selectively restricting of modifications to the schema comprises determining whether or not to implement deployments upon the entity and on a new entity based on a predicted likelihood of the deployments interrupting service on the middleware application system.

14. The non-transitory computer readable medium of claim 11 , wherein the entity comprises a software application or a software library; and the selectively restricting of modifications to the schema comprises preventing a deletion of components of the schema.

Assignments (2)
SECURITY INTEREST Recorded Jul 3, 2022
From: PALANTIR TECHNOLOGIES INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0506 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 4, 2021
From: DING, JAMES; SANTOS, GONÇALO SILVA; HELZBERG, RICHARD; PLAYFORD, THOMAS
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 057691/0021 →
Continuity (4)
Continuation 16586553 · Sep 27, 2019
Continuation 16221309 · Dec 14, 2018
Provisional Application 62750035 · Oct 24, 2018
Related Publication 20220027489A1 · Jan 27, 2022