7/8/2023 0 Comments Mpi vs grpc vs restIf you want to send an email, it’s hard to do in a RESTful way as there’s no resource to act upon. REST is not a great fit for domains where mapping concepts to resources is hard.This ambiguity has led the community to create more specific, opinionated frameworks like JSON:API, HAL, and OData. It doesn’t give you predefined answers to common questions like how to name resources, format JSON requests, include related resources, or implement paging. REST is a broad architectural style, as opposed to a concrete API framework or specification, and it leaves a lot of room for interpretation. REST requires requests to be cacheable whenever possible, and caching is implemented using HTTP’s native caching headers. When the client makes a request, it includes all information necessary for the server to process that request, and resends the information with subsequent requests if needed. REST is stateless - the server never stores the client’s state. It uses URLs to address resources and HTTP verbs ( GET, POST, PUT, DELETE, PATCH) to express the action to take. REST aims to follow HTTP semantics closely. REST can be defined as a stateless, cacheable, convention-based architecture for client-server interaction. REST was described way back in 2000 in Roy Fielding’s doctoral dissertation as the core architectural principle of the World Wide Web. REST (REpresentational State Transfer) is the most mature of the 3 API technology options.
0 Comments
Leave a Reply. |