graphql

And how do I then describe that object with GraphQL terms?

How do you get performance and not lots of nested queries out of GraphQL?

What's I'm missing from all the GraphQL examples seen out there is some kind of interaction with database.

I really suspect that the flexibility that GraphQL gives immediately translates to complexity on the server side.

Way I understand GraphQL is not as a replacement to SQL, otherwise you get hopelessly lost at implementing it.

User ID) and GraphQL and the view returns the subset of the view.

You might as well create a generic implemention, like GraphQL, which they did.

In essence, GraphQL query is a grocery list of stuff you want.

I wonder if this could easily be forked to provide a GraphQL interface to pg.

What would a GraphQL 'mutation' look like that kicked off some process requiring the identity of say 3/4 entities plus some of its own input?

GraphQL doesn't mean moving to stateful components, it's just a nicer way to have a singleton data store because instead of chunking and passing a map around, components can declare which data they need.

However we believe that intermediate application code is pretty critical to any GraphQL implementation.

For example GraphQL - the UI is "language" that "programs" what was traditionally the back-end API.

Actually, with GraphQL and now Om Next, you do put your data store "queries" in the component.

"user" and you apply it to the given GraphQL and get less fields than the view defined.

For example: class UserService { email() { if (this.context.user.id == this._id) return this._email else throw new CodedError(403, "Cannot request another users email") } } What is necessary now I think is an example open source app implemented with it to demonstrate how the stuff we do with regular APIs would work in GraphQL...