11327819

Microservices Mediation Layer for Canonical Message Alignment in Complex Microservices Environments

PublishedMay 10, 2022
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
20 claims

Legal claims defining the scope of protection, as filed with the USPTO.

1

1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory; the at least one processing device being configured to perform steps of: receiving in a microservices mediation layer a plurality of event notifications for respective internal events generated within an application; extracting information comprising at least a subset of an entity type, a key and an action from each of the event notifications; issuing at least one corresponding request to one or more microservices based at least in part on the extracted information; preparing at least one message based at least in part on one or more responses received from the one or more microservices; and publishing the at least one message to one or more message consumers.

2

2. The apparatus of claim 1 wherein the microservices mediation layer is configured to permit seamless switching between synchronous and asynchronous canonical message formats.

3

3. The apparatus of claim 1 wherein the one or more microservices comprise a plurality of synchronous microservices each returning a corresponding synchronous canonical message to the microservices mediation layer in response to a particular one of the issued requests.

4

4. The apparatus of claim 1 wherein the published message comprises an asynchronous canonical message that contains message payloads from respective ones of a plurality of synchronous canonical messages returned by respective synchronous microservices so as to provide canonical message alignment between the synchronous canonical messages and the asynchronous canonical message.

5

5. The apparatus of claim 1 wherein the published message comprises an asynchronous canonical message carrying at least one synchronous canonical message payload that is unmodified from one of the responses received from a corresponding one of the one or more microservices.

6

6. The apparatus of claim 5 wherein the asynchronous canonical message comprises an asynchronous canonical message header in addition to said at least one synchronous canonical message payload.

7

7. The apparatus of claim 1 wherein issuing at least one corresponding request to one or more microservices based at least in part on the extracted information comprises issuing multiple requests to respective ones of a plurality of microservices.

8

8. The apparatus of claim 1 wherein issuing at least one corresponding request to one or more microservices based at least in part on the extracted information comprises issuing at least one request to an aggregation microservice that issues multiple requests to respective ones of a plurality of microservices.

9

9. The apparatus of claim 1 wherein the application comprises a database application and a given one of the actions comprises at least one of an insert, an update and a delete.

10

10. The apparatus of claim 1 wherein the key comprises at least one of a primary key and a foreign key.

11

11. The apparatus of claim 1 wherein the microservices mediation layer is configured to perform one or more windowing operations in conjunction with preparing and publishing the at least one message so as to group together microservice responses relating to respective different event notifications occurring within a specified time period.

12

12. The apparatus of claim 1 wherein the microservices mediation layer utilizes a caching mechanism in which a time-to-live value is assigned to at least portions of the extracted information stored using the caching mechanism and at least a subset of the issuing, preparing and publishing are performed responsive to occurrence of an expiration event relating to the assigned time-to-live value.

13

13. The apparatus of claim 1 wherein the microservices mediation layer is configured to coordinate different windowing operations performed by different messaging publishing entities in preparing and publishing a single message conveying information that would otherwise be separately provided by the different message publishing entities.

14

14. The apparatus of claim 1 wherein publishing the at least one message to one or more message consumers comprises associating the message with a designated topic in a topic-based publisher-subscriber messaging model.

15

15. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device to perform steps of: receiving in a microservices mediation layer a plurality of event notifications for respective internal events generated within an application; extracting information comprising at least a subset of an entity type, a key and an action from each of the event notifications; issuing at least one corresponding request to one or more microservices based at least in part on the extracted information; preparing at least one message based at least in part on one or more responses received from the one or more microservices; and publishing the at least one message to one or more message consumers.

16

16. The computer program product of claim 15 wherein the microservices mediation layer is configured to permit seamless switching between synchronous and asynchronous canonical message formats.

17

17. The computer program product of claim 15 wherein the published message comprises an asynchronous canonical message that contains message payloads from respective ones of a plurality of synchronous canonical messages returned by respective synchronous microservices so as to provide canonical message alignment between the synchronous canonical messages and the asynchronous canonical message.

18

18. A method comprising: receiving in a microservices mediation layer a plurality of event notifications for respective internal events generated within an application; extracting information comprising at least a subset of an entity type, a key and an action from each of the event notifications; issuing at least one corresponding request to one or more microservices based at least in part on the extracted information; preparing at least one message based at least in part on one or more responses received from the one or more microservices; and publishing the at least one message to one or more message consumers; wherein the method is performed by at least one processing device comprising a processor coupled to a memory.

19

19. The method of claim 18 wherein the microservices mediation layer is configured to permit seamless switching between synchronous and asynchronous canonical message formats.

20

20. The method of claim 18 wherein the published message comprises an asynchronous canonical message that contains message payloads from respective ones of a plurality of synchronous canonical messages returned by respective synchronous microservices so as to provide canonical message alignment between the synchronous canonical messages and the asynchronous canonical message.

Patent Metadata

Filing Date

Unknown

Publication Date

May 10, 2022

Inventors

David J. Linsey
Lokajit Tikayatray

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “MICROSERVICES MEDIATION LAYER FOR CANONICAL MESSAGE ALIGNMENT IN COMPLEX MICROSERVICES ENVIRONMENTS” (11327819). https://patentable.app/patents/11327819

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.