Hi! I am spinning up a side project and am looking into some backend as a service solutions. As a backend dev in a larger organization I have always just build stuff using AWS and rolled our own, but now I want to iterate quickly and have some stuff built in at first.<p>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. Firebase looks cool, but I worry about using a NoSQL database in 2023. The AWS Amplify solution is tempting, but knowing AWS it will be clunky and require more time to administrate.<p>Does anyone have any suggestions or experience in using a BAAS? Thanks.<p>edit: I also have seen some hype on using Supabase which uses postgres, and a new firebase competitor named Convex which seems very new.
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.
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.
Full Disclosure, I'm one of the founders of WunderGraph, but I thought I provide my 2 cents.<p>> 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<p>We're open source with a Apache-2.0 license and will never switch it.<p>You can also self host it yourself on your architecture or you can host it on ours.<p>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.<p>Give it a try and let me know what you think!<p><a href="https://wundergraph.com/" rel="nofollow">https://wundergraph.com/</a>
[I work for Firebase]<p>One of the advantages we offer is ease of use backed up by GCP scale, reliability, and wide variety of additional products.<p>For example if you use Firestone and Cloud Functions with Firebase, you will still see your instances in GCP.<p>In that sense Amplify offers a similar experience but a higher complexity and a smaller community.
Hi y'all,<p>I'm building Singlebase.Cloud[1], the next generation BaaS, that will provide a NoSQL Datastore, Authentication, Storage, Search, Image processing, Analytics and more.<p>All with a friendly API to access and manipulate your data via SQL, GraphQL, REST.<p>Granted it's not a SQL DB, it provides a SQL interface to query and update your data.<p>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)<p>Let me know what you think of the idea.<p>[1]<a href="https://singlebase.cloud/" rel="nofollow">https://singlebase.cloud/</a>
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