Which GCP services to use - No SQL Options for storage (Memorystore, Datastore, Bigtable)

No SQL Options for storage : Memorystore, Datastore, Bigtable

1. Memorystore

  • managed in-memory database
  • USECASE
    • User-feature lookup in real-time bidding that requires submillisecond retrieval time.
    • Media and gaming applications that use precomputed predictions.
    • Storing intermediate data for a real-time data pipeline for creating input features.
  • Submillisecond retrieval latency on a limited amount of quickly changing data, retrieved by a few thousand clients, USE Memorystore.

2. Datastore

  • Fully-managed, scalable NoSQL document database built for automatic scaling, high performance, and ease of application development.
  • USECASE
    • Product recommendation system in an e-commerce site that's based on information about logged-in users.
  • Millisecond retrieval latency on slowly changing data where storage scales automatically, USE Datastore.

3. Bigtable

  • Massively scalable NoSQL database service engineered for high throughput and for low-latency workloads.
  • USECASE
    • Fraud detection that leverages dynamically aggregated values. Applications in Fintech and Adtech are usually subject to heavy reads and writes.
    • Ad prediction that leverages dynamically aggregated values over all ad requests and historical data.
  • Booking recommendation based on the overall customer base's recent bookings.
  • Millisecond retrieval latency on dynamically changing data, using a store that can scale linearly with heavy reads and writes, USE Bigtable.