3 ms·
I have never implemented GraphQL, so I can't speak from experience, there, but it does look pretty cool (if a bit "heavy"). I have implemented REST. I don't li
by ChrisMarshallNY 6y ago
I have never implemented GraphQL, so I can't speak from experience, there, but it does look pretty cool (if a bit "heavy").
I have implemented REST. I don't like "pure" REST, where POST, PATCH, and PUT statements are submitted as XML and/or JSON.
I tend to do what I term "REST-like," sort of the way most APIs seem to do, these days, where the sending methods are done similar to standard URI GET/POST stuff (URI arguments).
I tend to have responses come back as both JSON and XML, with a translator between them. XML is useful, because I can publish a schema, but otherwise, I prefer JSON.
But REST-like is quite simple. I don't need to bring in any dependencies to provide the API, so it's fast and lightweight.
But then, I have fairly humble servers. I suspect that GraphQL would be something I'd want for more ambitious servers.