Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by euyyn on Thursday April 27, 2017 @01:17PM
(#14213141)
I don't understand your point about third-party clients. APIs defined in .proto files can have both clients and servers implemented by anybody.
Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by daliwali on Thursday April 27, 2017 @01:51PM
(#14213403)
APIs defined in XMLRPC, CORBA, SOAP, et al, can have clients and servers implemented by anybody.
Programmers don't seem to learn from history and struggle with thinking over time. These formats worked well in a time when a single party (or second party) controls the server and client, when services were very consolidated. Now that the web is becoming more and more centralized and closed, it follows that RPC is making a comeback: widespread interoperability is not much of a concern.
Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by euyyn on Friday April 28, 2017 @11:31AM
(#14220217)
Sorry but you're not addressing your own point:
> RPC is a great fit if you are constrained to a single vendor and don't care about third-party clients
If I'm not constrained to a single vendor, and care about third-party clients, what makes RPC a bad fit? In specifics, not vague historical comparisons.
- HTTP APIs are worse than websites of the 90s. At least a browser could be expected to view a few websites. HTTP APIs require a custom client for each one.
- Document media types, not APIs. This isn't such a novel concept, browsers (fancy HTTP clients) work because HTML is a standard.
- Standards at the application layer, not specifications. You mentioned specs only.
Let me just clarify that RPC is a great fit if you are constrained to a single vendor and don't care about third-party clients. On the web, every browser is a third-party. For HTTP APIs to take off, they need to be built more like websites, or else vendor specs will fill every niche.