37 thoughts on “Firebase vs AWS Amplify

  1. What's the difference between Amplify vs Aurora vs MySQL vs DynamoDB…?
    And do all of them have the same function.

  2. Hi
    can someone explain..
    do we not need graphql with firestore?
    is there a use case to use graphql with firebase/firestore?
    or only with AWS amplify?
    thank you so much!!

  3. bro this is coming what to do?

    Failed to compile
    ./src/index.js
    Module not found: Can't resolve './App' in '/Users/saatyakthegreat/Downloads/react-firebase-chat-master 5/src'

  4. Amplify pros:
    – super easy user authentication out of the box
    – good documentation for all platforms (web, vue, react, ios, etc)
    Amplify cons:
    – DynamoDB was built for massive quantities of data so the relational model is proprietary and confusing
    – You can't get away with only using "Amplify".. you'll have to use other AWS services

    I dropped Amplify on my latest project and am so much happier back with Firebase. What Firebase does better than Amplify is its ability to totally abstract itself from the mothership (aka Google Cloud, and AWS for Amplify). You can go start to finish without leaving Firebase on your project. If you use Amplify, chances are you're going to need to branch into the overwhelming AWS-land.

  5. great video!

    despite people from comments are arguing AWS is hard to use, I think AWS amplify cool. Docs are really well explained, and I agree that UI is not that friendly.

    do you recommend me any getting started video or course of firebase ? I'm struggling a lot with their docs.

    cheers mate!

  6. Thank you for the nice video!

    In terms of pricing, Firebase is $0.6 read/ $1.8 write per one million query ?
    It seems that pricing of Firebase is based on 100,000.

  7. Does GraphQL require a "rigid" schema, that is, If I want to retrieve documents with some variations in the attributes in the same collection, can I read/write them with GraphQL, even when they don't match completely the schema in graphQL file?

  8. Firebase lets you attach a snapshot to a filtered collection, for example

    .firestore()
    .collection("collection")
    .where("user", "==", user.email)
    .onSnapshot(…)

    What would the equivalent be on amplify? As far as I can tell, your graphql subscription listens for all todo's, what if you wanted to only listen to those owned by a specific user?

  9. you definately need firebase for the analytics, crashlytics, and ads, amplify analytics is trash. however i personally use both firebase and amplify on the same app.

  10. You have to add the API-gateway (bridge between the client http call, websocket…) cost if you create a serverless API with AWS. So the cost per function is much more : 0.2 per million for lambda call + other lambda function cost + 1.2$ per million call (slightly more or less depending on the AWS region).

  11. I think there is a couple of features prices changed after you post the video such as the storage!
    I also have a question, if you plan to build an application that scale with 100K active users and more. do you think firebase a good choice?
    I found the sample price list on google firebase says 1M active users can cost 2900+$, does that really make sense?
    here is a linked https://firebase.google.com/docs/firestore/billing-example
    the above example for firestore only! but still does make sense?

  12. AWS yeah jump on it if u like missing documentation. I remember posting how to upload / dl an image (took me hours to figure out) to AWS bucket storage on ios SWIFT 3(I think) in 2016 on SO that made tens of K views / ups. Because their doc was simply not working …. and BTW, FS and cloud FS are so well conected that it REALLY makes serverless apps candy dev.

  13. as someone how has run a consultancy for a decade making dozens of production apps, honestly, this stuff is great for toys and learning but anyone using this in production should be shot. you should never hitch the success of your company to something so fragile. We have seen other services like this die out and giving google or amazon complete control over the inner working of your apps, data, and privacy is a recipe for absolute disaster.

Leave a Reply

Your email address will not be published. Required fields are marked *