Graphcool – Serverless GraphQL Back End

Re:Graphcool – Serverless GraphQL Back End by hobofan on Tuesday May 16, 2017 @06:03PM (#14353725)

Any plans for continous (read-only) direct database access? Without that, basically every modern BI solution can't be used. I think that besides the obvious lock-in, that's another big hinderance for building real products with Graphcool.

[ Parent | on HN ]

Re:Graphcool – Serverless GraphQL Back End by sorenbs on Wednesday May 17, 2017 @07:06AM (#14357296)

Hi hobofan :-)

This is something we are planning to support. We have two approaches, and I'm curious to hear what would work best for you.

1) Add an integration for selectively syncing data to s3. This would work very similar to the Algolia integration and allow you to transform the shape of your data. Tools like Athena and QuickSight can query directly against s3 buckets, and many other services can import data from s3.

2) Add the ability to provision a read replica and offer direct read-only sql access. This option would carry a higher fixed cost, so would not be appropriate for hobby projects.

[ Parent | on HN ]

Re:Graphcool – Serverless GraphQL Back End by tmoorai on Thursday May 18, 2017 @12:13PM (#14368451)

1) would a very good solution. It's adding the graph cool pieces to an existing data lake. From there anyone can do what she wants (Athena, Quicksight, Import into Redshift/BigQuery). Would love to see that.

BTW saw your talk today at AWS Summit in Berlin. Good job there.

[ Parent | on HN ]