<ul><li>ReST API design is more than just CRUD over HTTP.</li><li>The first step in ReST API design is deciding on the 'language' of the conversation.</li><li>The second step focuses on understanding the user's intentions.</li><li>The third step is to craft a dialogue.</li><li>Framing the cancellation process more thoughtfully can capture the humane aspect of the dialogue.</li><li>The cancellation process could be designed through a POST to a 'CancelledOrders' endpoint with a reason code or message.</li><li>CancelledOrders have advantages of reSTful purity, state representation, and extensibility.</li><li>An order canceller approach maintains the focus on the Order resource and is simpler.</li><li>The option to choose between resource-oriented and action-oriented approach depends on whether to prioritize conceptual clarity or operational simplicity.</li><li>The noun chosen should align with how the domain experts and API consumers naturally think.</li></ul>

ReST: It’s More Than Just CRUD Over HTTP

Discover more