Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I sometimes have to write integrations with external data providers (most of them being government agencies), and they love graphql, where (IMHO) it makes a lot of sense. They provide data about some entity¹ split into X fields, your application needs maybe 20% of them, and thanks to graphql you don't have to request anything but those 20%. When loading hundreds of millions of records, it saves you from loading, parsing, and then throwing away gigabytes of unnecessary JSON.

1: one example being tax records with all associated information about tax collecting agencies and taxpayers — it's a lot of data



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: