3 ms·
Don't wanna break it for you - but calling even a remote function exactly is "using an API" (application programming interface). I like the logo (or icon) they
by hexo 4y ago
Don't wanna break it for you - but calling even a remote function exactly is "using an API" (application programming interface).
I like the logo (or icon) they have, that masquerades it as some serious haskell (or some other functional PL) related project.
If it was this easy eveyone would be using RPC all over the place for many years already, and we'd have no HTTP and no train-load of other protocols.
- akiselev 4y ago> If it was this easy eveyone would be using RPC all over the place for many years already, and we'd have no HTTP and no train-load of other protocols. People are using RPC over HTTP all the time. Most backend APIs I've seen are only vaguely RESTful [1] and everyone seems to stuff much of their critical functionality in JSON RPC APIs masquerading as POST endpoints. [1] no true scotsman and HATEOAS ¯\_(ツ)_/¯
- brillout 4y agoThe reason RPC is making a comeback is because of 1. SSR (e.g. rendering React components to HTML on the server-side), and 2. the increased practice of continuous deployment. Increasingly, the frontend is deployed hand-in-hand with the backend. RPC is a match made in heaven for stacks where backend and frontend are deployed in-sync. There really are only two reasons for using a RESTful/GraphQL API: providing third parties access to your data (e.g. Facebook API) or decoupling frontend and backend (e.g. Netflix uses a loosely coupled microservice architecture). Most projects don't need either.