4 ms·
> You shouldn’t have to ship kilobytes of metadata describing your data schema to clients in order to fetch data. I feel like this requirement makes every othe
by lexicality 6y ago
> You shouldn’t have to ship kilobytes of metadata describing your data schema to clients in order to fetch data.
I feel like this requirement makes every other requirement impossible unless you use some kind of compiled language feature and even then you're not going to be able to have type safety without some kind of metadata.
Also, I don't think it's possible to make any one library that solves all "data fetching" scenarios. How could you reasonably live data (eg stock ticker), enormous data sets (eg looking through individual analytics events) slow but largely static lookups (eg searching a library catalog) and fast but uncachable (eg a SPA forum) into the same API without making it horrendous?
- lexicality 6y agoThat said, we do need some better standards. I look after a bunch of API integrations at work and we have everything from SOAP to GraphQL to downloading a magically named .xml.gzip file in a FTP directory with at least 10 other homemade REST implementation between and every single one of them is basically returning the same info but in wildly incompatible ways. At least the SOAP one crashes when they change the API without telling us :/