Topic 1 Question 18
You are building an API that will be used by Android and iOS apps. The API must:
- Support HTTPs
- Minimize bandwidth cost
- Integrate easily with mobile apps Which API architecture should you use?
RESTful APIs
MQTT for APIs
gRPC-based APIs
SOAP-based APIs
ユーザの投票
コメント(12)
In't C (gRPC) better because of the lower bandwidth (binary format)? It can be used in mobile apps and supports HTTP(s)
👍 8p42022/01/22To support HTTPS, minimize bandwidth cost, and integrate easily with mobile apps, you should use gRPC-based APIs (C).
gRPC (gRPC Remote Procedure Calls) is a modern, high-performance, open-source remote procedure call (RPC) framework that can be used to build APIs. It uses HTTP/2 as the underlying transport protocol and Protocol Buffers as the encoding format. gRPC is designed to be low-bandwidth, low-latency, and easily integrable with mobile apps. It also supports HTTPs out of the box.
RESTful APIs (A) are a popular choice for building APIs, but they may not be as efficient as gRPC in terms of bandwidth usage, especially for APIs that transfer large amounts of data. MQTT (B) is a lightweight messaging protocol that is often used in IoT applications, but it may not be as well-suited for building APIs as gRPC. SOAP-based APIs (D) are an older style of API that has largely been replaced by more modern alternatives like gRPC.
👍 3omermahgoub2023/01/01Agreed Option A is correct
👍 2Blueocean2022/01/22
シャッフルモード