Hacker News new | past | comments | ask | show | jobs | submit login

Pulsar dev here. There are certainly many similarities with what Kafka provides, though we made some different choices, especially for the storage layer.

The design has been heavily influenced by these traits: multi-tenancy, millions of topics, strong-durability, geo-replication, low publish latency (even when reading at max IO capacity), maintaining consumer position and, finally, operability (we need to replace machines, shift traffic and increase capacity seamlessly, without any user impact).

Storage apart, would you compare it to NATS? Is there something as latency sensitive as Pulsar or would you say it seems to be a leader in this prevalence? We see things like NSQ and NATS and we are never sure if latency is low enough for responding in an HTTP API with 1s timeout.

Registration is open for Startup School 2019. Classes start July 22nd.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact