Global Financial Trading Application | Minimizing Latency with Optimal Storage Option

Minimizing Latency for Global Financial Trading Application

Question

You are developing a financial trading application that will be used globally.

Data is stored and queried using a relational structure, and clients from all over the world should get the exact identical state of the data.

The application will be deployed in multiple regions to provide the lowest latency to end users.

You need to select a storage option for the application data while minimizing latency.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

https://cloud.google.com/solutions/best-practices-compute-engine-region-selection

The best storage option for this use case would be Cloud Spanner. Here's why:

  1. Relational structure: The data is stored in a relational structure, which means it requires a relational database management system (RDBMS) to manage the data. Cloud Spanner is a fully managed, relational database that is designed for scalability, consistency, and high availability.

  2. Global data replication: Cloud Spanner offers global data replication, which ensures that clients from all over the world get the exact identical state of the data. This is achieved through multi-region replication, where data is replicated across multiple regions in near real-time. This also ensures that the data is highly available and fault-tolerant.

  3. Low latency: The application will be deployed in multiple regions to provide the lowest latency to end users. Cloud Spanner offers low-latency access to data from any region, which makes it an ideal choice for a globally distributed application.

  4. High scalability: Cloud Spanner is designed to scale horizontally to meet the demands of large-scale applications. It offers automatic sharding of data, which means that the data can be partitioned across multiple nodes to improve performance and scalability.

On the other hand, Cloud Bigtable is a NoSQL database, which is not ideal for a relational data structure. Cloud SQL is a managed MySQL or PostgreSQL service, which is not suitable for globally distributed applications, and Firestore is a NoSQL document database that does not offer relational features.

Therefore, based on the above factors, Cloud Spanner would be the best option for this use case.