Rethinking REST API Design
Most APIs described as RESTful expose resources through HTTP, use familiar methods such as GET, POST, PUT, and DELETE, and return JSON representations. OpenAPI specifications document the available operations, while generated clients make them straightforward to invoke. This approach works well for many applications. But it raises an architectural question worth examining: How much does a client need to know about the server to interact with it? Consider an order management API. A client can create an order, retrieve it, pay for it, cancel it, or mark it as delivered. ...