Kafunk

By jet
Add to my DEV experience Queue

DISCONTINUED

Suggest alternative
Edit details
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
Sponsored

Kafunk Alternatives

Similar projects and alternatives to Kafunk

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Kafunk alternative or higher similarity.
Suggest an alternative to Kafunk

Kafunk reviews and mentions

Posts with mentions or reviews of Kafunk. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-04.
  • Walmart is migrating the remaining F# code into Java
    8 projects | news.ycombinator.com | 4 Mar 2024
    Performance.

    Generally speaking, F# was actually very fast, and had nice concurrency support, but there were times that wasn't the case.

    For example, in 2016 I was part of the initiative to rewrite the ad feed. We had to read in several Kafka topics, do some joining on our end, and emit to a separate Kafka topic. This isn't terribly hard to write, but we were dealing on the order of about ~100gb of data being pushed into memory. This is hardly "big data" stuff, but it's enough to highlight some issues.

    Specifically, the built F# persistent map structure was simply too slow to get the performance we wanted. I really like that structure, it's really handy and nice, but I ended up having to make heavy use of the ConcurrentDictionary that was built into .NET. This wasn't that hard or anything, but it made me a little sad that I had to move to a mutable store to get the performance I needed.

    There was also the fact that the `async` monad, while generally very good and useful, had bizarre bottlenecks that were hard to measure. It was difficult to know when the async task was actually started, and when you tried to measure performance bottlenecks you were really only measuring the scheduler, not the actual performance. This isn't really F#'s fault, this is an issue with any kind of cooperative scheduling system, but occasionally to get the performance we needed we'd have to move to lower level threads instead of the pretty monadic stuff. Microsoft eventually released the Task monad which generally performed a bit better.

    There were other things here and there; the Kafka client libraries for .NET simply aren't as good as the Java ones. Jet actually open-sourced their own (https://github.com/jet/kafunk) which did make it a bit more functional and nice, but it had performance issues as well, so a lot of us ended up using Confluent.

    There were little annoyances specific to F# as well; there's no real concept of a monad transformer, so if you wanted to do something like, for example, combine an Option and an Async into generalized syntax, you'd have to write your own wrapper monad thing, which wasn't that hard but was sort of ad hoc.

    The general rule of thumb was that the first draft of software, we would try and keep as functional and pretty. If that was too slow, we allowed mutation but only within a function. If that was too slow, we'd allow global mutation but only with thread-safe stuff.

Stats

Basic Kafunk repo stats
1
159
1.7
-

The primary programming language of Kafunk is F#.

Popular Comparisons

  1. Kafunk VS NetMQ
  2. Kafunk VS Hangfire
  3. Kafunk VS RawRabbit
  4. Kafunk VS RabbitMQ.NET
  5. Kafunk VS Rebus
  6. Kafunk VS NServiceBus
  7. Kafunk VS MassTransit
  8. Kafunk VS Confluent's .NET Client for Apache KafkaTM
  9. Kafunk VS AdaskoTheBeAsT.MediatR.SimpleInjector and AdaskoTheBeAsT.MediatR.SimpleInjector.AspNetCore
  10. Kafunk VS Enexure.MicroBus

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com