Skip to content

[Architecture]: Introducing eBPF #82

Description

@LorenzoTettamanti

Is your feature request related to a problem?

  • Yes

Problem Description

Sidecar proxies introduce significant overhead by adding extra complexity to the networking layer. If service A wants to communicate with service B, the message must pass through two sidecar proxies, like in the example below:
A --> Proxy A --> Proxy B --> B

Solution

By leveraging eBPF (Extended Berkeley Packet Filter), we can implement the networking layer directly at the kernel level, bypassing the user space and reducing the overhead introduced by sidecar proxies.

Additional Info

Demonstration of the communication:

Image

Image

Activity

  1. added
    rustPull requests that update Rust code
    ebpfeBPF related tasks
    help wantedExtra attention is needed
    on Mar 26, 2025
  2. added 5 commits that reference this issue on Apr 8, 2025
  3. added 3 commits that reference this issue on Apr 27, 2025
  4. 8 remaining items

  5. added 6 commits that reference this issue on May 14, 2025
  6. moved this from Todo to In Progress in CortexFlow v0.1on Jun 6, 2025
  7. moved this from In Progress to Permanent in CortexFlow v0.1on Jun 27, 2025
  8. moved this from Permanent to Not Planned in CortexFlow v0.1on Sep 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ebpfeBPF related tasksenhancementNew feature or requesthelp wantedExtra attention is neededrustPull requests that update Rust code

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions