An RPC-oriented API organizes its interface around named operations that perform actions. This style works well for stateless functionality but becomes harder to use when requests depend on stored state or prior calls. section 1.3
Stateful RPC interfaces can create practical consistency problems:
- Clients must memorize many subtly different methods, such as RescheduleFlight() and CancelReservation(). section 1.3
- Synonymous operations can receive inconsistent names, such as ShowAllFlights(), ListFlights(), and ListAllFlights(). section 1.3
- Standardized Create, Get, List, Delete, and Update operations reduce this variation by organizing methods around resources. section 1.3
Table 1.1 Summary of methods for an example flight-booking API (view table figure)
Compare the descriptive but inconsistent operations in a flight-booking RPC interface. section 1.3
