@kmx I think you showed me this at Heroku’s Waza a couples of years ago. If this is the same project, I am glad to see it is finally out in public. Nice work!
There was a time when I scoffed at the idea of building HTTP clients based on a schema. I thought that if the HTTP API was done correctly, it should be trivial to construct the client using a good HTTP client library. However, I am now thinking otherwise. Generating an HTTP client is boring. There are very fews ways to innovate an API client –so why we bothering? Let the machines do it.
I think WSDL left a bad taste for many of us. JSON Schema seems to be eminently easier to comprehend, and makes it straightforward to document a modern RESTful API.
I’ve also come to similar conclusions. Maintaining accurate documentation and update to date client libraries is very difficult at scale. I would love to have the hours back that I’ve wasted on maintenance.
The sneakers.io page claims faster performance than sidekiq. I suspect this is because sneakers is built on top of RabbitMQ whereas sidekiq is built on Redis.