Menu
I am writing a thesis which involves a comparison between RESTful web APIs and their corresponding alternatives. The problem is, I am quite biased towards REST and am failing to find any noteworthy architectural patterns that could be compared.
My comparison is going to analyze the patterns (or styles) from the consumer perspective (primarily how universal is an API for consumers).
Could you recommend me any alternatives for REST (as a software architectural pattern for comparison in the mentioned aspect? So far, I'm stuck with SOAP.
P.S. If the question is still too broad, I can narrow it down a bit.
882
REST APIs are obsolete. Fielding defined REST in his 2000 PhD dissertation “Architectural Styles and the Design of Network-based Software Architectures” at UC Irvine. Since then it has become the de facto for creating APIs.
“gRPC is roughly 7 times faster than REST when receiving data & roughly 10 times faster than REST when sending data for this specific payload.
SOAP is still used most often in the enterprise world, where communication between different services needs to conform to a set of rules and contracts. Because it follows objects, rules, and constraints, SOAP is a more strict protocol than REST.
Perhaps one aspect of RESTful APIs you may want to look for is "scalability". Do REST APIs scale? If they do, why do the companies below go their own way?
GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.
Falcor lets you represent all your remote data sources as a single domain model via a virtual JSON graph
145
In addition, an alternative to REST API is gRCP ( https://grpc.io/ ).
33
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
