bpf_buffer_per_source VS katran

Compare bpf_buffer_per_source vs katran and see what are their differences.

bpf_buffer_per_source

This UDP library lets a user specify a maximum buffer per source address received, so a single source cannot overwhelm a shared socket buffer. (by danielrh)

katran

A high performance layer 4 load balancer (by facebookincubator)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
bpf_buffer_per_source katran
1 3
0 4,552
- 1.1%
0.0 9.7
over 2 years ago 3 days ago
C C
BSD 2-clause "Simplified" License GNU General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

bpf_buffer_per_source

Posts with mentions or reviews of bpf_buffer_per_source. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-30.

katran

Posts with mentions or reviews of katran. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-30.
  • Investigating the impact of HTTP3 on network latency for search
    1 project | news.ycombinator.com | 22 May 2023
    HTTP/3/QUIC supports migrating connections between two networks, such as if a user switches from WIFI to LTE. IPVS or any UDP load balancer won't handle this scenario properly since it doesn't introspect the QUIC header and load balance based on the QUIC connection ID. This QUIC connection ID allows for a stable connection when the device needs to switch networks. If operators have any sort load balancer (like IPVS) between the client and the point the HTTP/3 connection is terminated, they will need to ensure that it has proper support for QUIC. One example is Katran[1] which has support for this method of load balancing.

    [1] https://github.com/facebookincubator/katran

  • Looking for some references or examples hyperscale load balancers
    1 project | /r/networking | 12 Feb 2023
    Also, Katran is open source: https://github.com/facebookincubator/katran
  • eBPF: A curated list of projects related to eBPF
    4 projects | news.ycombinator.com | 30 Aug 2021
    While I don't knwo the actual answer, a good place to look may be one of the eBPF load balancers like "Katran" from Facebook. I imagine it's needing to do that sort of thing. But no idea if it's attaching at the same level. I haven't really explained eBPF outside of tracing.

    https://github.com/facebookincubator/katran

What are some alternatives?

When comparing bpf_buffer_per_source and katran you can also consider the following projects:

awesome-ebpf - A curated list of awesome projects related to eBPF.

ebpfkit - ebpfkit is a rootkit powered by eBPF