Orlandster
Aug 26, 2017 · 1 min read

No words…

“In this article, we want to explore the differences between Firebase and GraphQL”

Feels not like exploring the differences. If this would be the case I would be able to build my own opinion. What you are trying to say is that Firebase is the ugly duckling and GraphQL the pink unicorn.

By the way, the whole text is full of silly comparisons. You cannot take a non-relational database and say the disadvantage is that there are no relations… or Firebase is bad, cz there are no queries… If you’re able to build the right database architecture you don’t need queries and this is an advantage believe me… And of course, you can build big projects. As I said it’s all about structure. I’m very curious if you have ever worked on a big project?

“Since the full requirements for an application are rarely known upfront”

of course, you know the technical requirements. Big companies spend so much on project management. They will not go freestyle.

“However, due to the unstructured nature of the data being stored, this API provides few guarantees about the data it delivers”

WTF! So you think JSON databases are unstructured. And data gets randomly returned or what?

I really can’t agree with this post. By the way, you can use GraphQL and Firebase together.

)

    Orlandster

    Written by

    Passionate Software Developer / Founder