crystal

Have you looked into PostGraphQL? https://github.com/postgraphql/postgraphql

This AWS announcement is quite exciting. For those wondering what else is available, I can share some recent research into available graphQL backend systems (but I have not used them past demo yet). These 3 hosted solutions all have a similar feature set. That includes support for enum types, uniqueness, required, and relations * GraphCMS * Scaphold * Graphcool GraphCMS is probably the most user friendly around schema creation, but that may not matter to you if you are an app developer. If you just want to declare a GraphQL schema there is Graph Front. There are also open source GraphQL backends * https://github.com/jscomplete/graphfront (Postgres) * https://github.com/postgraphql/postgraphql (Postgres) * http://join-monster.readthedocs.io/en/latest/ * https://rest-layer.io/ (MongoDB, Sqlite3, Google DataStore) You can als

similar, but for postgres : https://github.com/postgraphql/postgraphql

You're in luck, there are libraries that can do it for you! https://github.com/stems/join-monster And even a system that generates your whole schema: https://github.com/postgraphql/postgraphql Plus, the Graphcool framework allows you to bring your own DB: https://github.com/graphcool/framework

I haven't put anything into production yet but I've been playing with PostGraphQL (https://github.com/postgraphql/postgraphql). It automatically creates a GraphQL endpoint based on your schema using Node. You define your application logic as functions in your schema. It also can handle authentication for you. I'd definitely recommend checking it out.

similar but for GraphQl: https://github.com/postgraphql/postgraphql

GraphQL is something that's relatively simple (and brilliant) but is one of those things that you just need to try properly first for it to click, especially if you have a background of implementing tons of REST based services. The GraphQL related tools are top notch and implementing GraphQL server isn't any harder than a REST based server would be (one could even argue that it would be simpler). Even if you don't want to implement everything from scratch, tools like Postgraph[0] exists that pretty much automate it for you. I made a simple tutorial[1] on wrapping an existing API with GraphQL here which goes through basics of settings up too. [0] https://github.com/postgraphql/postgraphql [1] https://github.com/motleyagency/devday-tutorials/blob/master...

There's PostGraphQL, which serves a PostgreSQL database as a GraphQL schema: https://github.com/postgraphql/postgraphql

You might be interested in postgraphql: https://github.com/postgraphql/postgraphql Otherwise it depends on your GraphQL implementation and what DB adapters or ORMs they support. For example, `graphql-ruby` includes a generator for a Rails-compatible GraphQL schema.

Here's a project that might be interesting. https://github.com/postgraphql/postgraphql

There's also https://github.com/postgraphql/postgraphql

If you're willing to commit to Postgres, this package makes turning on a GraphQL API as simple as writing a couple lines of middleware: https://github.com/postgraphql/postgraphql

I hope you didn't just throw https://github.com/postgraphql/postgraphql and https://postgrest.com/en/v0.4/ behind some closed source code and called it a business.

I don't think it breaks down (as long as most of the data comes form the database). For example i know exactly how paymoapp.com (similar to basecamp) is structured , i consider it to be a fairly large system and i know for a fact that PostgREST can support that. As for the "very similar be done for GraphQL", there is https://github.com/postgraphql/postgraphql which was based on postgrest ideas. Another approach would be to build graphql on top of postgrest (my comment below)