Pub/Sub, simple + reliable + scalable = a great product
Overall Satisfaction with Google Cloud Pub/Sub
Our company currently uses Pub/Sub to reliably queue up messages that arrive rapidly from multiple instances. It's a very technical product and really only used by the development team rather than company-wide. The primary problem it addresses for us is its ability to handle scale and resilience in the case of errors.
Pros
- Highly scalable.
- Queues messages for up to 7 days if not acknowledged.
Cons
- Would be nice if the queue could be extended beyond 7 days.
- We found it a bit tricky replay unacknowledged messages when needed.
- Pub/Sub has helped avoid data loss improving our customer value prop.
- Pub/Sub has reduced development time that would otherwise be needed to build a highly scalable queue.
We considered several messaging platforms including Kafka and Kinesis but both would have required more developer work and didn't integrate as nicely with our ecosystem. RabbitMQ is another messaging platform I've researched and prototyped on; it also would have required more developer time to implement as well but might be a good alternative for a hobbyist or a team looking for more customization.
Do you think Google Cloud Pub/Sub delivers good value for the price?
Yes
Are you happy with Google Cloud Pub/Sub's feature set?
Yes
Did Google Cloud Pub/Sub live up to sales and marketing promises?
Yes
Did implementation of Google Cloud Pub/Sub go as expected?
Yes
Would you buy Google Cloud Pub/Sub again?
Yes
Comments
Please log in to join the conversation