3 ms·
You just keep thinking that until you see the god awful mess of REST apis that happens when you need to make an endpoint for every single slightly different que
by slaymaker1907 9y ago
You just keep thinking that until you see the god awful mess of REST apis that happens when you need to make an endpoint for every single slightly different query.
- linkmotif 9y agoYeah REST... it's for the truly patient and perseverant. Not to mention the pedantic. "REST principles"—heh. Also: JSON :(. Thank God GraphQL is changing this paradigm and has useable and even powerful clients already. Only bad thing about GraphQL is that it targets JSON but at least it's typed and schematic. But I guess we all benefited from REST, in the sense that it killed the whole 900-page XML book scene which was maybe the worst thing ever.
- rspeer 9y agoYeah, that's kind of how APIs have to work. It turns out it's not feasible or desirable to just let arbitrary people make arbitrary queries. SPARQL doesn't make it any more feasible, it just ignores feasibility.
- Vinnl 9y ago> It turns out it's not feasible or desirable to just let arbitrary people make arbitrary queries. GraphQL/Relay and Falcor are trying to make it feasible. And I think it's definitely desirable from a consumer point of view, at least.
- xg15 9y ago> It turns out it's not feasible or desirable to just let arbitrary people make arbitrary queries. It turns out where and why exactly?
- rspeer 9y agoDenial of service.
- derefr 9y agoYou can just 408-response queries after they execute for a given number of CPU cycles. And then rate-limit per-account using evercookies + browser fingerprinting + IP hashing. You can often disallow anonymous queries altogether, while you're at it; if your data is valuable, people are usually willing to register at least a pseudonymous account to get at it.