Re:Graphcool – Serverless GraphQL Back End
by revelation on Tuesday May 16, 2017 @01:06PM
(#14351228)
I thought it was the GraphQL equivalent of SQLite..
Please don't call yourself "Serverless" if your service goes down with the remainder of the world once AWS has some problem. Please don't call yourself "Serverless" if someone acquihiring you means my database disappearing from under me.
In other words, please don't call your service "Serverless" if it runs on a freaking server!
:-D
Based on the title, I also was expecting something that was designed to run client-side.
Serverless just means "as the user of this service, you don't need to worry-about/think-in-terms-of 'servers'".
It clearly doesn't mean 'no servers involved'.
Re:Graphcool – Serverless GraphQL Back End
by squeaky-clean on Tuesday May 16, 2017 @02:55PM
(#14352247)
It's kind of silly for them to compare themselves as "Serverless GraphQL Backend" vs "Backend-as-a-Service" on their homepage as if the two didn't mean exactly the same thing.
Not a really good choice for that word if you ask me.
Agreed. I was momentarily very confused when I clicked on the link thinking that this was some sort of pure client-side GraphQL library that was supposed to replace functions normally done on the server.