REST, GraphQL or RPC — A Decision Paralysis

This article explores the different aspects of API design and compares the REST, GraphQL, and RPC patterns. It discusses the considerations for schema definition, data model complexity, data updates, data types, filtering/sorting/pagination, environment/tooling, observability/scalability, error handling, versioning, and access controls. The author suggests that RPC is the future of API design, particularly for addressing complex use cases and decoupling implementation and data storage concerns.