IP Library Granted Patent US 11,057,487
Granted Patent B2
US 11,057,487 · App. 16/415,807 · Granted Jul 6, 2021

Systems and methods for recording metadata about microservices for requests to the microservices

Inventor: Jeremy White (Fort Lauderdale, FL)
Assignee: Citrix Systems, Inc.
H04L67/2804G06F16/1734H04L67/327
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,057,487
App. No.
16/415,807
Granted
Jul 6, 2021
Kind
B2
Abstract

Described embodiments provide systems and methods for recording metadata about a microservice for requests to the microservice. A device configured as a proxy to one or more microservices of a service can receive a registration request to register a microservice of the one or more microservices with the device. Metadata can be received during registration of the microservice with the device. The metadata can identify an identifier of the microservice, a deployment version of the microservice and a region of deployment of the microservice. The device can store the metadata in association with the microservice and record the metadata of the microservice registered with the device in association with a plurality of requests. The device can identify, via a user interface and the metadata recorded to the log, a change in operation of the microservice in connection with one of the deployment version or the region of the microservice.

Claims (31)

1. A method for recording metadata about a microservice for requests to the microservice, the method comprising:

(a) receiving, by a device configured as a proxy to one or more microservices of a service, a registration request to register a microservice of the one or more microservices with the device;

(b) receiving, by the device during registration of the microservice with the device, metadata provided by the microservice about the microservice, the metadata identifying a identifier of the microservice, a deployment version of the microservice and a region of deployment of the microservice, the device storing the metadata in association with the microservice;

(c) recording, by the device responsive to a plurality of requests to access the microservice, to a log the metadata of the microservice registered with the device in association with each of the plurality of requests; and

(d) identifying, by the device via a user interface based on the metadata recorded to the log and responsive to a comparison of metadata received with a response from the microservice to the metadata recorded to the log, a change in operation of the microservice in connection with one of the deployment version or the region of the microservice.

2. The method of claim 1 , wherein (a) further comprises routing requests to the one or more microservices to the device.

3. The method of claim 1 , wherein (b) further comprises receiving, by the device, the metadata one of as part of or included with the registration request.

4. The method of claim 1 , wherein (b) further comprises receiving, by the device during registration, from the microservice metadata comprising a product identifier, an operating system and an environment in which the microservice operates.

5. The method of claim 4 , wherein (d) further comprises identifying, by the device based at least on the log and processing of the at least one request at the microservice, the change in operation of the microservice attributable to one or more changes to the microservice identified by one of the product identifier, the operating system and the environment.

6. The method of claim 1 , wherein (c) further comprises receiving, by the device intermediary to the one or more microservices, the plurality of requests from one or more requestors.

7. The method of claim 1 , wherein (c) further comprises receiving, by the device, the plurality of requests one of routed or forwarded to the device.

8. The method of claim 1 , further comprising receiving, by the device, from the microservice one or more updates to the metadata of the microservice.

9. The method of claim 1 , wherein (d) further comprises identifying, by the device based at least on the log, an issue with operation of the microservice attributable to a change in the deployment version or the region of the microservice.

10. The method of claim 1 , wherein (d) further comprises identifying, by the device based at least on the log, an improvement in operation of the microservice attributable to one or more changes to the microservice identified in the metadata.

11. A system for recording metadata about a microservice for requests to the microservice, the system comprising:

a device comprising one or more processors, coupled to memory and configured as a proxy to one or more microservices of a service, the device configured to:

receive a registration request to register a microservice of the one or more microservices with the device;

receive, during registration of the microservice with the device, metadata provided by the microservice about the microservice;

wherein the metadata identifies an identifier of the microservice, a deployment version of the microservice and a region of deployment of the microservice, and wherein the device is configured to store the metadata in association with the microservice;

wherein the device is configured to:

record, responsive to a plurality of requests to access the microservice, to a log the metadata of the microservice registered with the device in association with each of the plurality of requests; and

identify, via a user interface based on the metadata recorded to the log and responsive to a comparison of metadata received with a response from the microservice to the metadata recorded to the log, a change in operation of the microservice in connection with one of the deployment version or the region of the microservice.

12. The system of claim 11 , wherein the plurality requests to the one or more microservices are routed to the device.

13. The system of claim 11 , wherein the device is further configured to receive the metadata as part of or included with the registration request.

14. The system of claim 11 , wherein the device is further configured to receive, during registration, from the microservice the metadata comprising a product identifier, an operating system and an environment in which the microservice operates.

15. The system of claim 14 , wherein the device is further configured to identify, based at least on the log and processing of the at least one request at the microservice, the change in operation of the microservice attributable to one or more changes to the microservice identified by one of the product identifier, the operating system and the environment.

16. The system of claim 11 , wherein the device is further configured to receive, intermediary to the one or more microservices, the plurality of requests from one or more requestors.

17. The system of claim 11 , wherein the device is further configured to receive the plurality of requests one of routed or forwarded to the device.

18. The system of claim 11 , wherein the device is further configured to receive from the microservice one or more updates to the metadata of the microservice.

19. The system of claim 11 , wherein the device is further configured to identify, based at least on the log, an issue with operation of the microservice attributable to a change in the deployment version or the region of the microservice.

20. The system of claim 11 , wherein the device is further configured to identify, based at least on the log, an improvement in operation of the microservice attributable to one or more changes to the microservice identified in the metadata.

Assignments (9)
PATENT SECURITY AGREEMENT Recorded Aug 15, 2025
From: CLOUD SOFTWARE GROUP, INC.; CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 072488/0172 →
SECURITY INTEREST Recorded May 24, 2024
From: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.); CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 067662/0568 →
RELEASE AND REASSIGNMENT OF SECURITY INTEREST IN PATENT (REEL/FRAME 062113/0001) Recorded Apr 14, 2023
From: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
To: CITRIX SYSTEMS, INC.; CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.)
Reel/Frame 063339/0525 →
PATENT SECURITY AGREEMENT Recorded Apr 14, 2023
From: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.); CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 063340/0164 →
PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 062113/0470 →
PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062112/0262 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 062113/0001 →
SECURITY INTEREST Recorded Sep 30, 2022
From: CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 062079/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2019
From: WHITE, JEREMY
To: CITRIX SYSTEMS, INC.
Reel/Frame 049850/0501 →
Continuity (1)
Related Publication 20200366752A1 · Nov 19, 2020