As a former user of Kafka, this is awesome and it would have been a huge help for our company if this was available then. I'm glad to hear that a company is offering Kafka as opposed to other propriety versions(AWS Kinesis etc).<p>One thing is odd though, there is no mention of disk space at all and only a configuration of retention time. One of Kafka's best features is the use of disk to store large amounts of messages, you are not RAM bound. Heroku seems to only allows you to set retention times? This could be awesome if they are giving you "unlimited" disk space, but could also be a beta oversight. Interested to see how this progresses.
> <i>What is Kafka?</i><p>> Apache Kafka is a distributed commit log for fast, fault-tolerant communication between producers and consumers using message based topics. Kafka provides the messaging backbone for building a new generation of distributed applications capable of handling billions of events and millions of transactions<p>Can anyone translate this into meaningful English for me?
I love Heroku and everything they are doing, it's doubtless a push forward for the web as a whole. However, the pricing for hobby sites (including SSL) is crazy from a personal point of view so I'm slowly moving my projects out of it [1][2]. I wish they had some kind of "Hobby Bundle".<p>[1] <a href="http://umbrellajs.com/" rel="nofollow">http://umbrellajs.com/</a>
[2] <a href="http://picnicss.com/" rel="nofollow">http://picnicss.com/</a>
Kudos to Heroku. As someone who has had to make Kafka into a managed service, I know what a pain it is (I'm not a Kafka fan for a lot of reasons) to administer in a cloud environment.
For anyone wanting to play with Kafka, Spotify's Kafka container was an invaluable resource for getting me up and running with Kafka. All the Zookeeper dependencies are taken care of allowing you to just start playing with Kafka right away.
<a href="https://github.com/spotify/docker-kafka" rel="nofollow">https://github.com/spotify/docker-kafka</a>
<a href="https://hub.docker.com/r/spotify/kafka/" rel="nofollow">https://hub.docker.com/r/spotify/kafka/</a>
This will be interesting to try out. I've used all the major cloud event/logging systems (Kinesis, Azure EventHubs, etc) and so far Google PubSub is the best in features and performance.<p>Only downside with Google Pubsub can be latency (which I'm working on fixing by building a gRPC driver) but Kafka has proven to be too complicated to maintain in-house. If heroku can provide the speed without the ops overhead, it'll be some good competition to Google's option.<p>Also want to note that Jay Kreps who helped build Kafka at LinkedIn is now behind <a href="http://www.confluent.io/" rel="nofollow">http://www.confluent.io/</a> which is like a better/enterprise version of Kafka.
For those wondering (all imo and only best guess)<p>The biggest advantage of kafka is that all of the heroku marketplace all of a sudden becomes "plug and play"<p>Essentially it's the "backend data" equivalent of what segment does for "frontend data".<p>Example: What's the benefit of having a graphDB service in the marketplace if most people dont want to / cant invest engineering in keeping the data in (realtime) sync.<p>With kafka they can establish standards that all partners can adapt to, they will simply offer piping of all heroku postgres/redis changes.
Does anyone know if Kafka has improved on their data loss issues since tested by Aphyr? <a href="https://aphyr.com/posts/293-jepsen-kafka" rel="nofollow">https://aphyr.com/posts/293-jepsen-kafka</a><p>A quote from the article: "At the end of the run, Kafka typically acknowledges 98–100% of writes. However, half of those writes (all those made during the partition) are lost."
I've wondered why there isn't a "big player" in the cloud space for this. Felt like a hole.<p>My operating theory is that the people who would really make use of something like this have grown beyond managed offerings and would take it in house. For smaller operations Redis is more than enough for pub/sub. Ditto for SQS for externally triggered eventing.
Can somebody provide a real-life use case for Kafka? I've seen comparisons between Redis, but what specifically does Kafka solve that Redis cannot?
The comments in this thread are funny;<p>Hey, what is Kafka?<p>"It's a distributed logging system, not a message queue"<p>Ok, what's the use case?<p><i>describes a case when its used as a message queue</i>