This sounds interesting but as someone outside this community, I would appreciate a little more background information. I have no idea what exactly the GraphQL API lets you do, what Apollo or Relay are, or even what language this is all in (guessing Javascript from the npm mention). Just linking some of these project names would be helpful, and some high-level motivation would be nice, like "GraphQL lets you make awesome interactive charts like this" or something.
Awesome way to leverage the schema definition files to set up a super fast server. I see this being really useful for quick prototyping or for hackathons.
While this is good, I'm astonished that this took so long, especially compared to Ruby On Rails. GraphQL was introduced 2 years ago, in the spring of 2015. And it's taken this long to get a CLI tool that can auto-generate some of the schema/setup?<p>These last 2 years, a lot of my clients have been asking me, "Should we switch to React/GraphQL?" And I've done one big project with GraphQL, in the spring of 2016. And I was amazed at how much I had to hand code, especially compared to Ruby On Rails.<p>In 2004, Ruby On Rails was born with these kinds of CLI tools. Indeed, Ruby On Rails pretty much established our modern ideas of how much a framework should do for us.<p>A CLI for GraphQL certainly makes the React eco-system more competitive with Ruby On Rails, but I am astonished that it took this long.<p>(PS: I am aware that React and Ruby On Rails are not strictly competitors, since you can use them together to create software/website. Nevertheless, "Should we use Ruby On Rails or React?" is a real question that I've been asked several times over the last few years.)
I looked at GraphQL..... can someone please explain how extensive join queries are done?<p>Literally almost every app I ever write, even the simple ones, offload tons of work to the database for joins between a half dozen tables.<p>I have yet to see a sane answer on how this is possible with GraphQL? How am I supposed to think about performance ... and not just having something overly simple/basic like HERES MAH BLOG... HERES DA COMMENTS!!!!!!
I think this will be a really awesome way for people to get a taste of GraphQL, without needing to write any code up front!<p>There are already some other tools that will give you a GraphQL API in very little code, but the fact that this one is hosted means you can host a frontend on GitHub pages or something, send it to your friends, and have a basic app going.
I'm new to GraphQL and I have been trying to get my friends as excited about it as I'm, the problem has always been the amount of code that they have to up-front before seeing any results, this might change that.<p>Definitively bookmarked!
The pricing LOL.. one of these is wrong, if not both.<p>its $45 for 2GB + 10m requests,
and $449 for 10GB + 50m requests. (more expensive per GB or requests..)
Damn, between this and sketch + create react native app, it's the week of 1-step-apps.<p>Is there an easy way to eject into a full blown graph.cool app? It seems you can't take any of your schema and use it as a starting point in graph.cool. From a business perspective, wouldn't that be the point? Perhaps I'm missing something though.