Jul 25, 2017 · 1 min read
I think your point is valid, tools like Swagger solve a lot of the problems that are mentioned in the article. However, I still think that GraphQL is superior to REST and will be the better choice for the majority of projects. If you need tools like Swagger that you put on top of REST to make sure it works well for your project — it seems like you just chose the wrong abstraction to build your backend. Of course you can work around many REST issues by including additional URL parameters or adjusting JSON payloads to be returned by the API endpoints to the client’s needs. But these approaches will always require a lot of work, are not standardized, won’t allows you to iterate quickly on products and don’t scale.
