Re:Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Se...
by bh13731 on Tuesday January 24, 2017 @02:35PM
(#13474693)
I've been using a similar service https://www.graph.cool for a while and it's been amazing. Good luck guys.
[ Parent
| on HN ]
Re:Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Se...
by sorenbs on Tuesday January 24, 2017 @04:33PM
(#13475744)
Thank’s for the support bh13731! If anybody has tried both Graphcool and Scaphold I would love to se an objective comparison between the two services.
Re:Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Se...
by k__ on Wednesday January 25, 2017 @06:02AM
(#13480393)
The UI of graph.cool is a bit clunky.
But the generated Schema is nice if you don't use Relay.
Re:Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Se...
by vning93 on Tuesday January 24, 2017 @02:45PM
(#13474779)
Thanks for the support! If you have some time, would love for you to check out Scaphold as well. With the latest release of our custom logic workflows, we're feature-complete and can handle real workloads that require advanced permissioning, real-time subscriptions, performance monitoring, and more.
Re:Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Se...
by k__ on Tuesday January 24, 2017 @04:01PM
(#13475399)
I liked your UI much more than the graph.cool thing.
But their generated Schema felt better to me. getUsers instead of this viewer stuff, feels much cleaner.
Re:Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Se...
by mparis on Tuesday January 24, 2017 @04:40PM
(#13475810)
Hey, so the reason for the viewer is due to the Relay spec. It's a standard that was developed at facebook that provides some best practices in terms of schema design but I understand liking the simpler schema especially if you use Apollo and not Relay. We've thought of providing a non-relay schema for this reason as well but have yet to get around to it. Thanks for the feedback.