I worked at startups (like, really really early stage Mickey Mouse ones, nothing serious) that used Firebase and Amplify. I think the toolchain for Amplify is nicer, but more dials means more mistakes can be made by juniors. Firebase's API is pretty clunky in my experience, and the docs aren't the best, but if you're building a something more in line with a CRUD app I don't think there's too much friction. That said I'd probably pick AWS because I like DynamoDB better than Firebase's Realtime DB or Firestore, and the managed backend is pretty easily understood. Maybe if analytics are important than Firebase has better integration there, but you could always just handle that externally on the app itself.
CockroachDB and Cloud Run. I absolutely would not start a new project on a database that’s not sharded by default.
Full Disclosure, I'm one of the founders of WunderGraph, but I thought I provide my 2 cents.
> The backend engineer in me is a little wary of using these and it seems like it will be hard to get off these platforms later
We're open source with a Apache-2.0 license and will never switch it.
You can also self host it yourself on your architecture or you can host it on ours.
What I like about WunderGraph personally is that it allows you to create your own firebase like toolkit with the tools you want, without getting locked into 1 vendor.
Give it a try and let me know what you think!
[I work for Firebase]
One of the advantages we offer is ease of use backed up by GCP scale, reliability, and wide variety of additional products.
For example if you use Firestone and Cloud Functions with Firebase, you will still see your instances in GCP.
In that sense Amplify offers a similar experience but a higher complexity and a smaller community.
Hi y'all,
I'm building Singlebase.Cloud[1], the next generation BaaS, that will provide a NoSQL Datastore, Authentication, Storage, Search, Image processing, Analytics and more.
All with a friendly API to access and manipulate your data via SQL, GraphQL, REST.
Granted it's not a SQL DB, it provides a SQL interface to query and update your data.
And for GraphQL, your data becomes the schema. There is no need to build a schema, whatever you throw at it, it will return it, if it exists in the response. Making the GraphQL a presentation layer. (I think it's cool)
Let me know what you think of the idea.
Supabase
Vercel for Next.js and Svelte deployments. Planetscale for MySQL hosting and scaling. Supabase for Postgres and extras.
Aws Lightsail is a lightweight version of aws. I find it handy for prototypes and small builds.
i would spin up dynamo table and lambda function if you doing prototype. can you provide more requirements? not sure what all you need in backend as service
Supabase is amazing
The only truely freeing BaaS is Pocketbase. You can write your custom code in Go and deploy a single binary. Absolute control, simplest of the solutions. It is as close to pure magic and I have tried all the other bases like Supabase, Hasura, NHost etc.