by sixwing on 4/27/16, 12:23 AM with 116 comments
by mbseid on 4/27/16, 3:13 AM
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.
by jonahx on 4/27/16, 1:42 AM
> 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
Can anyone translate this into meaningful English for me?
by franciscop on 4/27/16, 4:11 AM
by cachemiss on 4/27/16, 12:56 AM
by ChartsNGraffs on 4/27/16, 2:38 AM
by manigandham on 4/27/16, 2:08 AM
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.
Also want to note that Jay Kreps who helped build Kafka at LinkedIn is now behind http://www.confluent.io/ which is like a better/enterprise version of Kafka.
by andreasklinger on 4/27/16, 5:16 AM
The biggest advantage of kafka is that all of the heroku marketplace all of a sudden becomes "plug and play"
Essentially it's the "backend data" equivalent of what segment does for "frontend data".
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.
With kafka they can establish standards that all partners can adapt to, they will simply offer piping of all heroku postgres/redis changes.
by hmottestad on 4/27/16, 6:13 AM
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."
by koolba on 4/27/16, 1:50 AM
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.
by plunchete on 4/27/16, 12:57 AM
by nodesocket on 4/27/16, 2:02 AM
by jbob2000 on 4/27/16, 4:52 PM
Hey, what is Kafka?
"It's a distributed logging system, not a message queue"
Ok, what's the use case?
describes a case when its used as a message queue
by tibbon on 4/27/16, 1:56 AM
by mtw on 4/27/16, 1:20 PM
by tenismyanswer on 4/27/16, 10:29 AM
by elcct on 4/27/16, 7:37 AM