PostgREST
Related graphql implementations with similar concepts:<p>- <a href="https:&#x2F;&#x2F;www.graphile.org&#x2F;postgraphile&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.graphile.org&#x2F;postgraphile&#x2F;</a><p>- <a href="https:&#x2F;&#x2F;hasura.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hasura.io&#x2F;</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&#x2F;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 &#x2F; test story. For instance, the postgraphile examples have development scripts that constantly clear out the DB and no tests. Compared to Rails, it&#x27;s hard to imagine how you&#x27;d iterate on a product.<p>Are there other reasons this hasn&#x27;t seen more widespread adoption? Is there some inherent architectural flaw or just not enough incremental benefit?