"When we were looking at designing front-end applications, they only needed a small subset of that data," he said. "Most of them need the address and the lat/long, for example. Sending back all the information we have about every building every time would be very, very onerous. And so for us, it made sense to use GraphQL where the client could select exactly what data they wanted to get back."
Potential dumb question: this sounds like exactly the kind of the thing that any SQL database could handle well; what advantages are there to use GraphQL or similar in this context?
Biting the hand that feeds IT
