A financial services company stores financial data in Amazon Redshift. A data engineer wants to run real-time queries on the financial data to support a web-based trading application. The data engineer wants to run the queries from within the trading application.
Which solution will meet these requirements with the LEAST operational overhead?
To run real-time queries on financial data stored in Amazon Redshift with the least operational overhead, the best solution is to use the Amazon Redshift Data API. This API allows you to execute SQL queries directly from within your trading application over HTTPS, which eliminates the need to manage and maintain complex connection setups such as WebSocket or JDBC. This significantly reduces the operational overhead and provides an efficient, scalable way to interact with your data in real-time.
B. Use the Amazon Redshift Data API. Explanation: The Amazon Redshift Data API is a lightweight, HTTPS-based API that provides an alternative to using JDBC or ODBC drivers for running queries against Amazon Redshift. It allows you to execute SQL queries directly from within your application without the need for managing connections or drivers. This reduces operational overhead as there's no need to manage and maintain WebSocket or JDBC connections.
Real time queries with S3 are obviously BS. B it is: https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html
"The Amazon Redshift Data API enables you to painlessly access data from Amazon Redshift with all types of traditional, cloud-native, and containerized, serverless web service-based applications and event-driven applications." https://aws.amazon.com/de/blogs/big-data/using-the-amazon-redshift-data-api-to-interact-with-amazon-redshift-clusters/#:~:text=The%20Amazon%20Redshift%20Data%20API%20is%20not%20a%20replacement%20for,supported%20by%20the%20AWS%20SDK.
Inside application with minimal effort then using API would be correct
Even if you don't know nothing about them, you will still choose B because it seems the "LEAST operational overhead" :)
B is correct
B. DATA API