Many organizations choosing a data ingestion platform are curious about the benefits of Google Pub Sub vs. Kinesis (Google Cloud Pub/Sub vs. Amazon Kinesis). While both can be used to ingest data into cloud environments, they provide different service models for accomplishing this objective.
The first point of evaluation when considering Google Pub Sub vs. Kinesis is the ingestion model. Amazon Kinesis uses a streaming model, while its Google counterpart uses a publish and subscribe messaging model. Amazon Kinesis requires a certain amount of provisioning of “shards”, which must be scaled up when organizations need to increase bandwidth and throughput. The Google Pub Sub messaging approach, on the other hand, eliminates the need for provisioning.
When evaluating Google Pub Sub vs. Kinesis for administrative burden, Kinesis requires users to manually monitor usage and scale as needed, while Cloud Pub/Sub administrators need not monitor or scale anything manually.
When it comes to costs for Google Pub Sub vs. Kinesis, these two models provide additional distinctions. Cloud Pub/Sub is priced by data volume and users pay only for the resources they consume, while Amazon Kinesis is priced by shard hour, data volume and data retention period, and users pay for the resources they provision even if they are unused. Consequently, when comparing Google Pub Sub vs. Kinesis for costs, the Google platform tends to be less expensive.
