IP Library Granted Patent US 12,021,921
Granted Patent B2
US 12,021,921 · App. 17/976,351 · Granted Jun 25, 2024

Data plane reduction for eventing components

Inventor: Ahmed Abdalla Ibrahim Abdelrehim (Grasbrunn, DE)
Assignee: Red Hat, Inc.
H04L67/1001H04L41/12H04L67/53
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 12,021,921
App. No.
17/976,351
Granted
Jun 25, 2024
Kind
B2
Abstract

Systems and methods are described for configuring a data plane of an event streaming platform. An example method includes receiving a topology definition describing a topology of an event streaming platform, and generating, based on the topology definition, a Directed Acyclical Graph (DAG) that represents a data plane of the event streaming platform. The method also includes generating, via a processing device, a simplified data plane pathway based on the DAG, wherein the simplified data plane pathway eliminates intermediate hops between an event source and a final event destination described by the topology definition.

Claims (35)

1. A method comprising:

receiving a topology definition describing a topology of an event streaming platform;

generating, based on the topology definition, a Directed Acyclical Graph (DAG) that represents a data plane of the event streaming platform; and

generating, by a processing device, a simplified data plane pathway based on the DAG, wherein the simplified data plane pathway reduces intermediate hops between an event source and a final event destination described by the topology definition.

2. The method of claim 1 , further comprising generating an event message at the event source and sending the event message directly to the final event destination in a single hop.

3. The method of claim 2 , wherein generating the event message comprises generating a hypertext transfer protocol (HTTP) CloudEvent message.

4. The method of claim 1 , further comprising receiving the topology definition from a user describing a series of eventing components.

5. The method of claim 1 , wherein the event streaming platform is at least partially implemented as a Knative event streaming platform.

6. The method of claim 1 , further comprising generating a plurality of data plane pathways which includes the simplified data plane pathway, wherein each ingress service of the topology is associated with one of the plurality of data plane pathways.

7. The method of claim 1 , wherein the topology of the event streaming platform comprises an event broker to implement an event filter, and wherein generating the simplified data plane pathway comprises implementing the event filter at the event source.

8. The method of claim 1 , further comprising receiving an updated topology definition describing a new topology of the event streaming platform and, responsive to the receiving:

generating, based on the updated topology definition, an updated DAG that represents an updated data plane of the event streaming platform; and

generating a new simplified data plane pathway based on the updated DAG.

9. A system comprising:

a memory; and

a processing device operatively coupled to the memory, the processing device to:

receive a topology definition describing a topology of an event streaming platform;

generate, based on the topology definition, a Directed Acyclical Graph (DAG) that represents a data plane of the event streaming platform; and

generate a simplified data plane pathway based on the DAG, wherein the simplified data plane pathway reduces intermediate hops between an event source and a final event destination described by the topology definition.

10. The system of claim 9 , wherein the processing device is further to generate a hypertext transfer protocol (HTTP) CloudEvent message at the event source and send the HTTP CloudEvent message directly to the final event destination in a single hop.

11. The system of claim 9 , wherein the processing device is further to receive the topology definition from a user describing a series of eventing components.

12. The system of claim 9 , wherein the event streaming platform is at least partially implemented as a Knative event streaming platform.

13. The system of claim 9 , wherein the processing device is further to generate a plurality of data plane pathways which includes the simplified data plane pathway, wherein each ingress service of the topology is associated with one of the plurality of data plane pathways.

14. The system of claim 9 , wherein the topology of the event streaming platform comprises an event broker to implement an event filter, and wherein to generate the simplified data plane pathway comprises to implement the event filter at the event source.

15. The system of claim 9 , wherein the processing device is further to receive an updated topology definition describing a new topology of the event streaming platform and, responsive to the updated topology definition:

generate, based on the updated topology definition, an updated DAG that represents an updated data plane of the event streaming platform; and

generate a new simplified data plane pathway based on the updated DAG.

16. A non-transitory computer-readable medium, having instructions stored thereon which, when executed by a processing device, cause the processing device to:

receive a topology definition describing a topology of an event streaming platform;

generate, based on the topology definition, a Directed Acyclical Graph (DAG) that represents a data plane of the event streaming platform; and

generate, by the processing device, a simplified data plane pathway based on the DAG, wherein the simplified data plane pathway eliminates intermediate hops between an event source and a final event destination described by the topology definition.

17. The non-transitory computer-readable medium of claim 16 , further comprising instructions to cause the processing device to generate a hypertext transfer protocol (HTTP) CloudEvent message at the event source and send the HTTP CloudEvent message directly to the final event destination in a single hop.

18. The non-transitory computer-readable medium of claim 16 , further comprising instructions to cause the processing device to receive the topology definition from a user describing a series of eventing components.

19. The non-transitory computer-readable medium of claim 16 , wherein the event streaming platform is at least partially implemented as a Knative event streaming platform.

20. The non-transitory computer-readable medium of claim 16 , wherein the topology of the event streaming platform comprises an event broker configured to implement an event filter, and wherein to generate the simplified data plane pathway comprises to implement the event filter at the event source.

Assignments (2)
CHANGE OF NAME Recorded Mar 3, 2026
From: RED HAT, INC.
To: RED HAT, LLC
Reel/Frame 074913/0759 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2022
From: ABDELREHIM, AHMED ABDALLA IBRAHIM
To: RED HAT, INC.
Reel/Frame 061584/0945 →