While REST exists since the 2000s and became popular due to the software architectural switch from monoliths to microservices, RPC has its origin in earlier SOA infrastructures and was the preferred API used in distributed systems.

REST offers an entity driven approach of fetching and manipulating resources with HTTP methods and payload (mostly CRUD), while RPC is command or function driven and less strict.

Due to its resource focused structure and limited number of HTTP methods the REST paradigm is often used incorrectly by developers and result in APIs that look like RPC endpoints.

For developers it is still hard to create an API that follows the REST principles. The question arises if we should allow a RPC based API design for non CRUD-based microservices.

The aim of this talk is to change the attitude of architects and developers towards REST-based APIs and allowing more flexibility in designing HTTP based APIs.