Need advice about which tool to choose?Ask the StackShare community!
AWS Amplify vs Firebase: What are the differences?
Introduction:
When deciding between AWS Amplify and Firebase for building web applications, it's essential to understand the key differences to make an informed decision. Both platforms offer significant features and services that cater to a wide range of needs, but they differ in their approach and capabilities.
Backend Infrastructure: AWS Amplify provides a platform that allows developers to access and manage various AWS services, such as Lambda, API Gateway, and DynamoDB, for building scalable and secure backends. On the other hand, Firebase offers a fully managed backend service, including real-time database, authentication, and cloud functions, making it easier for developers to set up and maintain backend infrastructure without dealing with individual AWS services.
Scalability: AWS Amplify leverages the extensive infrastructure of AWS, allowing applications to scale seamlessly based on traffic demands. Firebase, on the other hand, provides automatic scaling capabilities; however, it may not offer the same level of scalability as AWS Amplify for highly complex and demanding applications.
Authentication: Firebase offers a straightforward authentication and user management system out-of-the-box, making it easy to integrate features like email/password authentication, social logins, and anonymous sign-ins. AWS Amplify also provides authentication services but may require additional configurations and setup compared to Firebase, especially for complex authentication workflows.
Real-time Database: Firebase is well-known for its real-time database, which uses WebSockets to provide synchronous data updates. This feature enables developers to create real-time applications easily. On the other hand, AWS Amplify supports GraphQL APIs for real-time data updates, offering a more structured approach for building real-time applications.
Serverless Functions: AWS Amplify integrates seamlessly with AWS Lambda functions, allowing developers to run serverless code in response to events. Firebase, on the other hand, allows developers to create and deploy cloud functions that seamlessly integrate with other Firebase services, providing a serverless computing environment for running backend code.
Integration with Other AWS Services: AWS Amplify offers tight integration with various AWS services, providing developers with a comprehensive toolkit for building and managing web applications. Firebase, while it offers a range of services, may not have the same level of integration with other Google Cloud Platform services as AWS Amplify does with AWS services.
In Summary, understanding the key differences between AWS Amplify and Firebase is crucial for choosing the right platform based on your project requirements.
We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.
I would recommend looking hard into Firebase
for this project, especially if you do not have dedicated full-stack or backend members on your team.
The real time database, as you mentioned, is a great option, but I would also look into Firestore
. Similar to RTDB, it adds more functions and some cool methods as well. Also, another great thing about Firebase is you have easy access to storage and dead simple auth as well.
Node.js
Express
MongoDB
Socket.IO
and Apollo
are great technologies as well, and may be the better option if you do not wish to cede as much control to third parties in your application.
Overall, I say if you wish to focus more time developing your React
application instead of other parts of your stack, Firebase
is a great way to do that.
Hello Noam 👋,
I suggest taking a look at Ably, it has all the realtime features you need and the platform is designed to guarantee critical functionality at scale.
Here is an in depth comparison between Ably and Firebase
Hey Noam,
I would recommend you to take a look into 8base. It has features you've requested, also relation database and GraphQL API which will help you to develop rapidly.
Thanks, Ilya
Firebase is the most powerful platform that I saw to support an MVP stage of a project that implies a website + mobile applications.
Be careful with what I say there: "to support an MVP". Firebase is awesome for early stages, but it has some huge technical problems.
Let's talk now about the PROS:
- With a few clicks, you have a full platform, with an AWESOME free tier, ready to be used. Serverless support for static files (your website in JS, probably), backend support for realtime DB, or even Google Cloud Functions made simple (Firebase Functions).
- Probably one of the most important things: You can integrate Analytics, and Push Notifications to your Android and iOS app with a few clicks.
- NoSQL DB (this may also be consider as a CONS. Careful here.
- With Firebase Functions, it's super simple to have global vars in memory, to speed up the backend responses
- Awesome support with Expo (awesome technology for mobile MVPs)
- Super simple local testing. Just run
firebase init
and thennpm run serve
and you'll have your backend running in your local env. - Huge Authorization+Authentication integrated flows: Login with Facebook, Gmail, and all the other options, with just a couple of minutes of configurations and barely few lines of code.
Now, some CONS:
In Firebase Firestore DB (the DB you'll probably use): Compound queries are not allowed. For example, you can NOT do this:
.where("state", ">=", "CA").where("population", ">", 100000)
. You can't combine different attributes of the object in thewhere
query. Read more about that limitation in https://firebase.google.com/docs/firestore/query-data/queries#compound_queriesIn Firebase Functions: OR querys (like
where user_status = 2 OR user_status = 3
in SQL) are not allowed. Yes... This is HUGE. Not be able to do an OR query is a huge blocker in performance. Luckily in the last months Firebase added an "IN" query, where you can do.where('country', 'in', ['USA', 'Japan'])
but it's limited to only 10 values in thein
array. Good enough, but still some limitations there. Check more about that limitation in https://firebase.google.com/docs/firestore/query-data/queries#in_not-in_and_array-contains-any
Feel free to ask any question, and I'll share some details here
Pros of AWS Amplify
- GraphQL5
- Better with Relations and Security3
- Flexible Auth options2
- Cheaper2
- Backed by Amazon1
- Config free environment variables1
- Continuous deployment1
- Jije0
Pros of Firebase
- Realtime backend made easy371
- Fast and responsive270
- Easy setup242
- Real-time215
- JSON191
- Free134
- Backed by google128
- Angular adaptor83
- Reliable68
- Great customer support36
- Great documentation32
- Real-time synchronization25
- Mobile friendly21
- Rapid prototyping19
- Great security14
- Automatic scaling12
- Freakingly awesome11
- Super fast development8
- Angularfire is an amazing addition!8
- Chat8
- Firebase hosting6
- Built in user auth/oauth6
- Awesome next-gen backend6
- Ios adaptor6
- Speed of light4
- Very easy to use4
- Great3
- It's made development super fast3
- Brilliant for startups3
- Free hosting2
- Cloud functions2
- JS Offline and Sync suport2
- Low battery consumption2
- .net2
- The concurrent updates create a great experience2
- Push notification2
- I can quickly create static web apps with no backend2
- Great all-round functionality2
- Free authentication solution2
- Easy Reactjs integration1
- Google's support1
- Free SSL1
- CDN & cache out of the box1
- Easy to use1
- Large1
- Faster workflow1
- Serverless1
- Good Free Limits1
- Simple and easy1
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Amplify
- Free tier is limited2
- Steep Learning Curve1
Cons of Firebase
- Can become expensive31
- No open source, you depend on external company16
- Scalability is not infinite15
- Not Flexible Enough9
- Cant filter queries7
- Very unstable server3
- No Relational Data3
- Too many errors2
- No offline sync2