A pattern language for RESTful conversations

Interface Responsibility Patterns

“…If the computation is resource-intense (CPU, RAM), algorithm and distribution design might have to be rethought to avoid bottlenecks and single points of failure; see conversation pattern Long-Running Request [35]. While not directly observable in the functional API contract, this is critical for the API design because it may affect the ability to meet its Service Level Agreement (SLA) [40].…”

“…The client sends its input via a request message queue, and the API provider puts the output on a response message queue [19]. • Call followed by callback: the input is sent via a first call, and the result is sent via a callback, which assumes that clients support callbacks [43] • Long running request (input is posted, a link is provided where the progress can be polled, eventually the result is published at its own link -there is an optional but useful opportunity to use the link to cancel the request and clean up the result when no longer needed) [35].…”

“…Steps 5 and 6 of the demo "Domain-Driven Service Design with Context Mapper and MDSL" 35 • Apply a recognized analysis and design practice to identify…”

“…Instances of this pattern may participate in long running and therefore stateful conversations [17]. They can use and go along with one or more of the RESTful conversation patterns from [35]. For instance, one may want to consider factoring out the state management and the computation part of the pattern into separate services.…”

“…https://martinfowler.com/eaaDev/EventSourcing.html35 https://ozimmer.ch/practices/2020/06/10/ICWEKeynoteAndDemo.html…”