Firebase vs. SQLite

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Firebase
Score 8.4 out of 10
N/A
Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
SQLite
Score 9.6 out of 10
N/A
SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is one of the most widely deployed databases in the world.N/A
Pricing
FirebaseSQLite
Editions & Modules
Phone Authentication
$0.01
Per Verification
Stored Data
$0.18
Per GiB
No answers on this topic
Offerings
Pricing Offerings
FirebaseSQLite
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
FirebaseSQLite
Considered Both Products
Firebase
Chose Firebase
Supabase is more user-friendly especially since it is directly integrated with Lovable, one of the most popular AI coder for non-technical users.
Chose Firebase
Supabase seems to have the best of all worlds right now. Followed by MongoDB/Firebase for smaller projects requiring less manpower and resources. Azure and Microsoft are reserved for existing projects and larger corporate clients.
Chose Firebase
Although there are other backend platforms that could have provided us with a solution to our project. The way of grouping the solution in FIREBASE, atomizing in the same project the database, cloud functions, authentication, push notifications, etc., has given us a clearer …
Chose Firebase
Unlike other tools in the GCP suite that have an equivalent in other clouds such as Bigquery (Athenas on AWS), AI Platform (Sagemaker), Storage (S3), we do not find an equivalent as complete as Firebase in any other provider. This is the main reason why we chose this provider …
Chose Firebase
Firebase came to a multiuse case for our product for authenticating backend services, users on the app & get data on the user base using the dashboard.
Chose Firebase
Firebase has a single NoSQL database, it is a simple, powerful and uniform application development platform in connectors, it has multiple programming languages ​​such as JavaScript and necessary tools that will simplify the creation of applications.
Chose Firebase
Firebase poses great documentation and integration with Android devices. And it's very good as well for iOS ones. So, for these scenarios, Firebase becomes the ideal ally.
Chose Firebase
It eases the app development process, has an extensive database that allows you to store media files in the cloud, supports robust uploads and downloads, and login authentication on any platform.
Chose Firebase
PostgreSQL is a relational database and is well suited for complex applications, however, Firebase is well suited for light and faster applications.
Chose Firebase
Firebase is easy to manage and scale really well for web application services. It offers better authentication and is easy to implement. For real-time analytics on web applications, it works very well. Firebase offers more features compared to other services especially it can …
Chose Firebase
  • User interface and console are very easy to understand
  • There is no pain in Integration with IOS, Android, and unity platforms
  • Cost-effective
Chose Firebase
We choose Firebase for various reasons:
  • A large set of resources and world-class Google support.
  • Pricing was a larger role in this decision.
Chose Firebase
If I get a suitable budget next year, I'll be switching us to Adobe Analytics. Their app/web tracking and the interface are streets ahead of Firebase.
Chose Firebase
Firebase is a much more comprehensive tool. While Fabric only had user traffic and trends data, it did not have the user communication set of tools. While CleverTap has CRM tools, it does not have tools for developers and product teams. While Adobe Analytics is good with …
Chose Firebase
I haven't played much with Heroku beyond deploying projects from Github. It looks to be very similar in providing a cloud-based platform for developing and deploying web apps as quickly as possible. I would look at comparing both of these before choosing a solution. I am just …
Chose Firebase
We chose Firebase for the following reasons.
  • Online resources.
  • Comes with better support.
Chose Firebase
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted …
Chose Firebase
Firebase does a lot of things well, but Branch.io does a lot of things great. We originally chose Firebase because it was free, had great crash reporting, and full event tracking. As we began to scale, increase paid marketing spend, and implement features such as journey …
Chose Firebase
It's tough to pick out competitors against Firebase as I'm really unsure and doubt there's another product exactly like it. As mentioned before Firebase literally does everything you can imagine for a mobile application but doesn't get insanely deep in one feature or action. It …
Chose Firebase
Firebase is well suited for projects with simpler database workloads that require its real-time features. For data that is heavily read in real time, it's a great choice and gives developers a lot of features that would have been complicated and time-consuming to build up front …
SQLite
Chose SQLite
I also use other Database Systems, but for small apps with offline storage, SQLite is a good and easy to use Database.
Chose SQLite
SQLite is faster and also Light weight as compared to Microsoft SQL Server. Also being open source it reduces the application development cost drastically
Chose SQLite
SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data …
Chose SQLite
We looked at other traditional RDBMS products, but found them to be cumbersome to deploy. They take up more space, and consume more computing resources than SQLite does. While the performance or direct integration to our primary applications may have been better or easier if we …
Chose SQLite
SQLite has many types of queries to do CRUD operations. and even do manipulation to external files as well. it is fast and easy to implement compared to other Databases.
SQLite support atomic behaviours, so app crash in any situation, the won't impact database or data within …
Chose SQLite
Microsoft SQLExpress: More heavyweight, not as lean in terms of disk space or processing requirements. Involves Microsoft's tentacles to be involved.
Chose SQLite
SQLite is considered better against these two depending on the needs and phase of the project. If we require a lightweight yet reliable database which should also be portable across different platforms and speed is the most important part of the query and data security is not …
Chose SQLite
I think there is no real competition between them.
In "SQLite" you can hear "light" when you don't need to store a big amount of data and when you need something easy to deploy, SQLite is a good choice, I didn't find those qualities in other database systems I knew.
Chose SQLite
When looking at the original items available, Valentina was a serious contender. What was good about SQLite was the familiar SQL interface and way it accessed data. Valentina, at the time, had issues with index corruption requiring vigilance with the database maintenance making …
Chose SQLite
SQLite stacks quite well against Microsoft SQL server management studio however we need the Microsoft security for our data MDSN documentation is poor but available.
Best Alternatives
FirebaseSQLite
Small Businesses
Visual Studio
Visual Studio
Score 9.1 out of 10
InfluxDB
InfluxDB
Score 8.8 out of 10
Medium-sized Companies
Visual Studio
Visual Studio
Score 9.1 out of 10
Neo4j
Neo4j
Score 9.8 out of 10
Enterprises
Visual Studio
Visual Studio
Score 9.1 out of 10
Neo4j
Neo4j
Score 9.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
FirebaseSQLite
Likelihood to Recommend
7.0
(0 ratings)
10.0
(0 ratings)
Usability
7.0
(0 ratings)
9.0
(0 ratings)
Support Rating
7.3
(0 ratings)
1.0
(0 ratings)
Configurability
-
(0 ratings)
10.0
(0 ratings)
Ease of integration
-
(0 ratings)
10.0
(0 ratings)
User Testimonials
FirebaseSQLite
Likelihood to Recommend
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
Read full review
The portability and ease of use has us doing local development, and then shipping the database to production for implementation. This compact deliverable object is great. Until multiple developers need to access it at a time. It is a caveat, but we create a database per integration as it is easier to manage. Using a SQLite database to manage more than one integration or task is not something we would recommend.
Read full review
Pros
  • Extremely robust. Has about any tool you can think of under one roof making it extremely useful as a backup platform for data analytics or small teams that need something quickly.
  • Intuitive and easy UI/UX. Being made and owned by Google, you expect nothing less. Very easy to use for anyone that has any marketing or analytical experience especially in Google Analytics (which I just assume all marketers do).
  • Safe, secure, and sturdy. Never need to worry about downtimes or misinformation as it's as clean and safe as it is being run by Google.
  • FREE! What else is there to say. Unless you're an extremely large application handling hundreds of thousands to millions of users, this pay as you go plan will stay free.
Read full review
  • Our products are using SQLite in embedded Linux and in Windows software.
  • It is truly a stable cross-platform database.
  • The fact that it is a zero-configuration database engine, it is particularly a nice advantage when you work in the embedded world.
  • Being a single database file, it provides ease for those who need to quickly transfer data to someone else, or quickly browse data.
Read full review
Cons
  • Firebase/Firestore has very limited support for querying more complicated items; for example, performing a simple string search is not possible.
  • While upfront costs are low, costs can grow quickly if you're not careful about what you are being billed for.
  • Dashboards have at times shown different information to what is billed, and support from Google is less than stellar and not as effective as that from Amazon or Microsoft.
Read full review
  • Although it is excellent at what it does, you should be really careful and plan accordingly if you know that your database is going to scale at a huge level because it is not suitable of databases which are of Enterprise level and demands top-notch security and protection.
  • If your project involves multiple people working on the same database simultaneously, then that becomes a big problem, because it only allows single write at one time. You really need to be forward thinking in a manner to predict if this database will cater to all the needs of your project.
  • The most common difficulty with this is the lack of some of the basic functionality which is present in the other premier databases like Joints, Stored Procedure calls, Security and permission grants. If you do require all those things then you are better off not using this software.
  • Lastly, if you are using this in an Andriod App development cycle then also your options are limited because it does not integrate with PostgreSQL and MYSQL.
Read full review
Usability
Firebase functions are more difficult to use, there are no concepts of triggers or cascading deletes without the use of Firebase functions. Firebase functions can run forever if not written correctly and cause billing nightmares. While this hasn't happened to us specifically it is a thing that happens more than one realizes.
Read full review
I have had a wonderful experience with SQLite because in my every project I use SQLite in the development phase because it's really fast, doesn't crash and very easy to maintain as well. It saves a lot on physical memory and dedicated server usage. It has all the basic functionality you would need to get the job done and that too at no cost at all. What more could you ask for !!!
Read full review
Support Rating
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
Read full review
I haven't needed support yet.
Read full review
Alternatives Considered
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
Read full review
SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data it contains. The user interface is best for input and output. It's best for developing skills and project deliverables.
Read full review
Return on Investment
  • Firebase has been able to help us understand reliably, the drop-off in our user flows with their funnel feature. This has made it easy for us to be able to pinpoint weaknesses in our funnel and test and optimize with data as the dependent variable.
  • From an economic standpoint, we don't pay for Firebase which is great, but as the saying goes "You get what you pay for" also holds true in this context. As we looked to grow and scale, we looked for a paid solution.
  • From a developer resource standpoint, Firebase has been extremely easy to integrate into our app. Whether it be the event tracking, dynamic links or crash reporting we have not had to waste too much developer time thanks to their well-organized developer docs.
Read full review
  • No licensing fees has a net increase on ROI
  • The active community has kept support costs low, further increasing ROI
  • The wide range of supported platforms and high level of compatibility has increased ROI by reducing time spent porting the database model to any platform specific solutions.
Read full review
ScreenShots