| - | GraphQL | REST | 
|---|---|---|
| Architecture | Client-driven | Server-driven | 
| Organized in terms of | Schema & type system | Endpoints | 
| Operations | Query Mutation Subscription  | 
          Create Read Update Write  | 
        
| Data fetching | Specific data with single API call | Fixed data with multiple API calls | 
| Community | Growing | Large | 
| Performance | Fast | Multiple network calls take up more time | 
| Development Speed | Rapid | Slower | 
| Learning Curve | Difficult | Moderate | 
| Self-documenting | Using introspection. | - | 
| File uploading | Very challenging | - | 
| Web caching | via libraries built on top | - | 
| Stability | Lesser error prone: automatic validation and type checking | Better choice for complex queries | 
| Use cases | Multiple micro-services Aggregators Mobile Apps  | 
          Simple apps Resource driven apps  | 
        
Friday, October 16, 2020
GraphQL vs REST?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment