I'd like to see a blow by blow comparison of Twitter DistributedLog vs Kafka vs Pulsar.
Particularly focusing on what each solution means by "geo-replication" ,what geo consistently guarantees are made, how operable the geo rep features are in practice etc. At first glance those interested in not losing data and interested in geo-replication and constituency are better off going with DistLog rather than either of the other two solutions.
However if all you care about is a single DC then K is simpler as long as you are happy for consumers to track offsets.
But if you want broker side delivery tracking then perhaps go with Yahoo or kafka with lazy commits of offsets to zk.
However if all you care about is a single DC then K is simpler as long as you are happy for consumers to track offsets.
But if you want broker side delivery tracking then perhaps go with Yahoo or kafka with lazy commits of offsets to zk.