Hacker News Reader

Comment by EGreg | Hacker News Reader

Seems like another way to lock you into a proprietary cloud (Firebase or AWS backend).

Why not just take a client side library and an open-source backend, and host it on EC2 or some general purpose computer server hosted anywhere? This way your CLIENTS have a choice too.

If you can install Wordpress why not this?

SAFE network will solve all this soon.

View on HN

I avoid EC2 instances as much as possible. If you are just using a cloud provider to host your VMs, you’re really not taking advantage of “being in the cloud”.

As far as lock in, it’s just like “providing a facade over your database access so you. n change databases. Few people ever change database backends.

Hey, if you are looking for an open source alternative, checkout daptin [1]. The graphql api is on the way [2]

[1] https://github.com/daptin/daptin

[2] https://github.com/daptin/daptin/pull/28

It’s built on AWS primitives, so while there is some lock in there, it’s not as bad as being tied to Firebase’s backend.

I think the lock-in can be rather small if you consider the flexibility of GraphQL.

Having used graph.cool I can say there's a significant amount of lock-in. Authorization can be pretty specific to the implementation and often impacts your schema. Secondly the extensions that have a lot of the logic are implemented differently every time. AppSync uses Apache Velocity Template Language (VTL), seems like a huge lock-in there. Don't be fooled by the GraphQL sticker, there's a significant amount of lock-in if you go with any of the SaaS(BaaS) products.

Reply on news.ycombinator.com