|
|
|
|
|
by sorenbs
3082 days ago
|
|
PostGraphile is super cool. Especially if you like centralising logic at the database level. There are pros and cons to this approach. Personally I prefer keeping my database layer as simple as possible - no stored procedures, no queues and certainly no communicating to external systems. But I still see great value in generating a GraphQL data API and using that as the only way to interact with the database. GraphQL Bindings is a new technology that allows you write a server that acts as an advanced proxy in front of another GraphQL API. It allows you to recompose the schema, and intercept requests for specific queries or mutations. Using an approach like this you can pass through queries to PostGraphile almost unmodified while taking full control over mutations. It's early days, but we have a pretty cool setup that generates TypeScript type definitions based on the underlying GraphQL API. And it is all open source :-) https://blog.graph.cool/reusing-composing-graphql-apis-with-... |
|