Not for everyone. Each programmer has their own appreciation of what is good coding music.
(From most influential to least)
Not for everyone. Each programmer has their own appreciation of what is good coding music.
(From most influential to least)
bin/kafka-topics.sh --zookeeper localhost:2181 --list
bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic mytopic
bin/kafka-topics.sh --zookeeper localhost:2181 --alter --topic mytopic --config retention.ms=1000
... wait a minute ...
PUT test_index | |
{ | |
"settings": { | |
"number_of_shards": 1, | |
"number_of_replicas": 0, | |
"analysis": { | |
"analyzer": { | |
"test_analyzer": { | |
"type":"custom", | |
"tokenizer": "whitespace", |
End-to-end Latency | |
0.0543 ms ms (median) | |
0.003125 ms (99th percentile) | |
5 ms (99.9th percentile) | |
Producer and consumer | |
Producer - 1431170.2 records/sec (136.49 MB/sec) | |
Consumer - 3276754.7021 records/sec (312.4957 MB/sec) |
When deciding between Memcached and Redis, here are a few questions to consider:
OK, you can pretty much ignore what I wrote below this update, because it doesn't really apply anymore.
I wrote this over a year ago, and at the time I had spent a couple of weeks trying to get Kafka 0.8 working with .NET and then Node.js with much frustration and very little success. I was rather angry. It keeps getting linked, though, and just popped up on Hacker News, so here's sort of an update, although I haven't used Kafka at all this year so I don't really have any new information.
In the end, we managed to get things working with a Node.js client, although we continued to have problems, both with our code and with managing a Kafka/Zookeeper cluster generally. What made it worse was that I did not then, and do not now, believe that Kafka was the correct solution for that particular problem at that particular company. What they were trying to achieve could have been done more simply with any number of other messaging systems, with a subscriber reading messages off and writing
# Edit this file then run `update-haproxy haproxy-servers.cfg`. | |
# Alternatively, use a shell pipeline to build server list `... | update-haproxy`. | |
server demo1 127.0.0.1:8001 check cookie demo1 weight 100 | |
server demo2 127.0.0.1:8002 check cookie demo2 weight 100 | |
server demo3 127.0.0.1:8003 check cookie demo3 weight 0 | |
server demo4 127.0.0.1:8004 check cookie demo3 weight 0 |
import java.io.FileDescriptor; | |
import java.io.FileOutputStream; | |
import java.io.IOException; | |
import java.io.OutputStream; | |
import java.io.PrintStream; | |
public class HelloWorld{ | |
private static HelloWorld instance; | |
public static void main(String[] args){ | |
instantiateHelloWorldMainClassAndRun(); |