crystal

The pitch on the project page for Schema Driven APIs[0] mentions "hide implementation details with views of your data" (as in CREATE VIEW) and "automatic relations with the REFERENCES constraint". Do both of these work together? E.g. could I create an "api" schema that consists entirely of views that query other schema(s), but still have the relations automatically determined? https://github.com/calebmer/postgraphql#schema-driven-apis

I'm nearing completion of a real world commercial application of some complexity that uses this along with React Relay. I knew SQL but not PostgresSQL coming into the project. I can say that this has been a joy to work with. This is how I will be building apps for the a while now. Huge thanks to Caleb Meredith for all the work he has done on https://github.com/calebmer/postgraphql

A quick search of the Github issues seems to indicate that PostGraphQL does suffer from the N+1 query problem at least to some extent (https://github.com/calebmer/postgraphql/issues/219). Which probably doesn't matter as long as you only have a few nested children, but might seriously kill performance for some cases. I always find it disappointing when that much of the power of a database like Postgres is thrown away by an abstraction. I find the general approach of PostGraphQL (and Postgrest, which is a similar project for a Postgres REST API) very interesting, it would be nice if it also generated reasonable queries for this kind of data.

Cool, hadn't seen that. There is also postgraphql, which I have become a big fan of and is a great foundation: https://github.com/calebmer/postgraphql That said, the real-time aspect is what I'm really dying for, plus a company supporting a BAAS. The ease of firebase is so nice, and you can make really cool real time apps with it very fast. I'm not sure if switching to a relational model would make impose some technical limitation that json stores don't (besides obvious complexity). Postgraphql + socket.io is kind of what i'm thinking is the start

I've never done it, but I think it's possible to do this in Postgres as well using LISTEN and NOTIFY. You may want to do all of your database mutations through functions that ultimately call NOTIFY for this to work though. But uh, that's how you'd do it in postgraphql or postgrest anyway. https://github.com/calebmer/postgraphql http://postgrest.com/

By client-side state, I mean user interactions that affect variables used across the app that don't need to be persisted. Relay doesn't do that yet, as it only deals with persisted data. @josephsavona[1] and @wincent[2] are the guys putting information out about Relay 2. Greg Hurrell (@wincent) did a talk[3] about it in August. And since I'm linking to related resources, I just want to add a plug for an awesome project a friend is working on (and we're putting it into production on my startup project). @calebmer/postgraphql[4] let's you get a free GraphQL API from a PostgreSQL schema. [1]: https://github.com/josephsavona [2]: https://github.com/wincent [3]: https://www.youtube.com/watch?v=OEfUBN9dAI8 [4]: https://github.com/calebmer/postgraphql

If you are going with React I suggest you go all in, i.e. React + Relay + GraphQL. In FB words "While each of these technologies — React, Relay, and GraphQL — are powerful on their own, the combination is a UI platform that allows us to move fast and ship high-quality apps at scale" The tricky part is the GraphQL/backend server. You can roll your sleeves and do it yourself starting form this https://github.com/graphql/graphql-js Might also try https://github.com/calebmer/postgraphql (PostgREST inspired, open source but no auth and has N+1 problem) I am also working on a tool/platform that you might be interested for the backend (in beta). It is based on OpenResty/PostgREST/PostgreSQL and it will give you a REST and GraphQL (Relay compatible) backend with very little work. http://graphqlapi.com/ https://github.com/ruslantalpa/sub0_sample_a

Also check Postgraphql: https://github.com/calebmer/postgraphql Inspired from Postgrest linked above, it automatically builds a GraphQL API by reflecting on postgres schema.

Definitely, PostgREST is an awesome project and definitely an inspiration for PostGraphQL. I gave the project credit in the README: https://github.com/calebmer/postgraphql#thanks

I really like the README in this project. I had a lot of questions (especially going to production and extending GraphQL myself) which are answered in the README. https://github.com/calebmer/postgraphql/blob/master/README.m... But I don't know how to do it yet.