Hi ryanschneider
This is a very interesting model we are actively exploring. The primary issue is that the cost of the minimum infrastructure required to run Graphcool in the scalable and fault-tolerant way we have designed our architecture is too high to make it feasible for most projects. We are offering this option on the enterprise plan, but that's a very different price point than our publicly listed plans.
Re:Graphcool – Serverless GraphQL Back End
by ryanschneider on Tuesday May 16, 2017 @06:18PM
(#14353827)
Maybe it's a hybrid approach where most of the load is handled by the SaaS "mothership" but users could opt-in to running additional AWS Marketplace nodes in their own infrastructure to have more direct access to their data? This could also answer hobofan's request for a solution to BI integration.
Re:Graphcool – Serverless GraphQL Back End
by sorenbs on Wednesday May 17, 2017 @07:12AM
(#14357321)
I think that is a very valid approach. We use https://buildkite.com/ for ci and they have exactly that model, where they manage the admin panel and meta data db, but worker nodes can be deployed elsewhere
Re:Graphcool – Serverless GraphQL Back End
by user15672 on Wednesday May 17, 2017 @07:42AM
(#14357479)
For something like this I'd have thought you'd be better off ignoring services like this and getting a Terraform setup going. Lambda functions are pretty simple to push out and it wouldn't require you to have some additional third party cruft in the middle:
https://www.terraform.io/docs/providers/aws/r/lambda_functio...
That seems like the best scenario: I have access to the infrastructure if necessary, and am paying for the value add of the service over-and-above AWS (or Google/Azure). If they stop supporting it, all my instances/lambda functions/etc are still my own.
edit: typo