728x90
- Use REST if:
- You’re building a CRUD-style web application.
- Your API is mostly manipulating well-structured related data.
- Your API needs to be highly cacheable, including support for intermediate proxy caching.
- Use gRPC if:
- Your API is private and powers communications between parts of a microservices architecture.
- Your API is mostly about actions.
- You need to collect data from IoT devices.
- You’re implementing a Backend For Frontend pattern for a mobile application with stable API request patterns.
- Performance is a critical requirement.
- Use GraphQL if:
- You’re building a public API and you want it to be highly flexible in terms of customizing requests.
- You want to defer defining your API surface until you have a chance to analyze which resources your clients tend to request.
- You want to aggregate internal data from multiple sources into a public API for multiple clients with varying data requirements.
https://speedscale.com/choosing-an-api-technology-grpc-rest-graphql/
'software engineering > backend' 카테고리의 다른 글
MongoDB - 집계 (0) | 2023.06.18 |
---|---|
Locking - Optimistic concurrency control (OCC) (0) | 2022.08.31 |
ElasticSearch (0) | 2022.08.29 |
DynamoDB (0) | 2022.08.29 |
Query on S3 ( Athena, Redshift ) (0) | 2022.08.29 |