11–20 of 114 posts
Whoa! This is a game changer! I was looking into both Kafka and Google Pub/Sub for a event-oriented system my team was designing. Google Pub/Sub looked very promising, but no guarantee of ordering was a deal breaker for us. I’ll consider this more strongly for the next system we build.
What did you pick? I'm interested in non-G solutions.
"Receiving messages in order might increase latency." It would be good to know what sort of overhead we are looking at here; very interested in this feature
And do messages without an ordering key incur the same overhead?
Disclaimer: I work on Pub/Sub.
Whoa! This is a game changer! I was looking into both Kafka and Google Pub/Sub for a event-oriented system my team was designing. Google Pub/Sub looked very promising, but no guarantee of ordering was a deal breaker for us. I’ll consider this more strongly for the next system we build.
We used Pub/Sub very extensively (50B messages a day) but moved to Pulsar [0]. It performs equally well and has some nice features. And also no vendor lock-in. [0] https://kesque.com/billions-of-events-a-day-without-breaking...
"Receiving messages in order might increase latency." It would be good to know what sort of overhead we are looking at here; very interested in this feature
Earlier quoted context omitted.
We used Pub/Sub very extensively (50B messages a day) but moved to Pulsar [0]. It performs equally well and has some nice features. And also no vendor lock-in. [0] https://kesque.com/billions-of-events-a-day-without-breaking...
Given cloud vendors low respect for their customers, the proper stance is to own your own infrastructure.
Whoa! This is a game changer! I was looking into both Kafka and Google Pub/Sub for a event-oriented system my team was designing. Google Pub/Sub looked very promising, but no guarantee of ordering was a deal breaker for us. I’ll consider this more strongly for the next system we build.
Whoa! This is a game changer! I was looking into both Kafka and Google Pub/Sub for a event-oriented system my team was designing. Google Pub/Sub looked very promising, but no guarantee of ordering was a deal breaker for us. I’ll consider this more strongly for the next system we build.
What's a use case where strict ordering is critically important?
- Create A
- Delete A
In one ordering, A is created and then deleted as expected, in the other, the delete fails but then A is created and remains.
Head of line blocking as a service!
Whoa! This is a game changer! I was looking into both Kafka and Google Pub/Sub for a event-oriented system my team was designing. Google Pub/Sub looked very promising, but no guarantee of ordering was a deal breaker for us. I’ll consider this more strongly for the next system we build.
What's a use case where strict ordering is critically important?