An online brokerage company requires a high volume trade processing architecture. You need to create a secure queuing system that triggers jobs. The jobs will run in Google Cloud and call the company's Python API to execute trades. You need to efficiently implement a solution. What should you do?
To design a secure, efficient, and scalable queuing system that triggers jobs which call the company's Python API to execute trades in Google Cloud, you can use a Pub/Sub push subscription to trigger a Cloud Function. This setup allows for high volume message processing, immediate execution of trades upon receiving market data, and seamless integration with the Python API. This method ensures low latency, scalability, and cost optimization by leveraging Google Cloud's serverless computing features.
A and D are both good. I go for A because we have high volume and easy to scale and optmize cost
Ans A https://cloud.google.com/functions/docs/calling/pubsub#deployment
Because trading platform requires securely transmission to queuing If you use cloud compose then we need some other job to trigger composer … would that be cloud composer api or cloud function …
Answer A: assume, Company wants to buy immediately in same second if stock goes down or up. Somehow, it is connected to PubSub as SINK connector, then immediately there is PUSH to subcriber (cloud function) that is connected to their python API (internal application) that makes the purchase.
A. Use a Pub/Sub push subscription to trigger a Cloud Function to pass the data to the Python API.
A is the answer.
Answer is D, at work we use solution A for low volume of Pub/Sub messages and Cloud function, and using D Composer for high volume Pub/Sub messages.
A might be enough. Cloud composer will be an overkill
A because D is stupidly high latency
D is the answer.
A. more sense to me.
Composer support exception and retry for complex pipeline. D might be correct
D is a more recommend way by Google, IMO.
I agree, at work use solution A for low volume of Pub/Sub messages and function, and using Composer for high volume Pub/Sub messages.
Vote A, can't see the need for composer
https://cloud.google.com/functions/docs/calling/pubsub
A. Use a Pub/Sub push subscription to trigger a Cloud Function to pass the data to the Python API.