Storage options and their use cases in GCP
This read I will try to give a few good reasons to choose your storage option in GCP as per your use case.
Cloud Datastore: Consider using Cloud Datastore if you need to store unstructured objects or if you require support for transactions and SQL-like queries. This storage service provides terabytes of capacity with a maximum unit size of one megabyte per entity.
Cloud Datastore is the best for semi-structured application data that is used in app engines’ applications.
Cloud Bigtable: If you need to store a large number of structured objects. but this does not support SQL’s queries nor does it support multi-row transactions. This storage service provides petabytes of capacity with a maximum unit size of 10 megabytes per cell and 100 megabytes per row.
Bigtable is best for analytical data with heavy read/write events like AdTech, Financial or IoT data.
Cloud Storage: Consider it if you need to store immutable blobs larger than 10 megabytes such as large images or movies.
This storage service provides petabytes of capacity with a maximum unit size of five terabytes per object.
Cloud Storage is best for structured and unstructured, binary or object data like images, large media files, and backups.
Cloud SQL or Cloud Spanner: If you need full SQL support for an online transaction processing system.
Cloud SQL provides terabytes of capacity, while Cloud Spanner provides petabytes.
If Cloud SQL does not fit your requirements because you need horizontal scalability not just through read replicas, consider using Cloud Spanner.
Cloud SQL is best for web frameworks and in existing applications like storing user credentials and customer orders.
Cloud Spanner is best for large scale database applications that are larger than two terabytes; for example, for financial trading and e-commerce use cases.
BigQuery: The usual reason to store data in BigQuery is to use its big data analysis and interactive query and capabilities.
