PostgREST
Related graphql implementations with similar concepts:<p>- <a href="https://www.graphile.org/postgraphile/" rel="nofollow">https://www.graphile.org/postgraphile/</a><p>- <a href="https://hasura.io/" rel="nofollow">https://hasura.io/</a><p>Love the idea of having APIs flow out of a single set of schema definitions. The Rails style of speccing a model, migrations, and controller/serializer or graphql types feels overly verbose and repetitive.<p>To me the biggest thing these groups could do to speed adoption is flesh out the feature development / test story. For instance, the postgraphile examples have development scripts that constantly clear out the DB and no tests. Compared to Rails, it's hard to imagine how you'd iterate on a product.<p>Are there other reasons this hasn't seen more widespread adoption? Is there some inherent architectural flaw or just not enough incremental benefit?