What is Firebase?
Who uses Firebase?
Firebase Integrations
Here are some stack decisions, common use cases and reviews by companies and developers who chose Firebase in their tech stack.
Dear Team, Please advise the stack to be used for building Chat Applications that cater to billions of users and work on Mobile as well as desktop. I don't want to use Firebase since it is not fitting into my use case of not using third Party Service Provider. I am comfortable with Java/PHP as a backend. Can we consider RethinkDB, MySQL, and GunDB for the application?
Also looking for Push methodology and not polling one for sending Realtime updates.
Regards Sukesh
I am trying to build a delivery application on Flutter, however, I am having difficulty deciding on which backend I need to choose, as Firebase is going to be very expensive.
Should I use Pouchdb or Firebase?
I want to store text documents and notes. Most of them are very short, just a means of tracking information while I'm doing research.
I want to be able to access them from multiple locations, preferably through a web browser but that is not a necessity.
I've also considered putting my information in a text document or word document but I would like to be a little more formal about the process.
Hello,
I'm in the midst of reviewing an old CRUD SAAS I have running on Angular 7 with a MariaDB backend and Laravel PHP. Presently is hosted on a couple of Linode servers- and really feeling the weight, especially with the looming need to upgrade to A15 and meet the pace and scalability occurring (for context, the SAAS turns in over 24k USD monthly in subscriptions- so I have concerns around the impact of a new stack on existing clients). Additionally, I manage a Kotlin and Swift codebase for appdev.
I'm looking at moving towards Flutter for a singular codebase, and something serverless but still relational- like Supabase. In the past, I ran my own Auth services- but it was a ton of work to setup and maintain, so looking at using Firebase for Auth services (I know Supabase has Auth as well, but I wonder if it's as reliable and frequently maintained as Firebase?) Supabase has a FlutterSDK as well which makes things much simpler. Planning on maintaining microservices like Stripe etc for functional aspects.
I would love some insight from those who have done a tech stack transition, what should I be aware of- those who have produced in Flutter or a similar stack, what am I walking into without knowing?
I recently make an IoT app with Flutter, Firebase that can control and get data from Esp8266 sensor. The next semester I want to make an app IoT app with more features and I have a question can Firebase good enough or do I need to learn how to host a server, DB?
I need some advice about idea for IoT project and the question above.
We are planning to build a local-based app to provide custom-prepared food based on subscriptions.
This app will have three main parts: a mobile app made with React Native, a web app made with React, and GraphQL API.
The main functionality is providing menus to clients based on their food preferences. This is not real-time but weekly-based.
We will need also a storage place for documents and images. We would love to have fewer services as possible.
The team is made by fullstack JavaScript developers which means mostly experienced with MongoDB. What we are still considering is:
- Use Firebase (easier, has storage, is good for mobile) or MongoDB Atlas (already experience with it, easy to use, flexible. Not sure about storage tho) but with Mongo I am concern about storage system. I know MongoDB can store large file but I wonder if is good practice. Where Firebase as storage as service.
- if we choose MongoDB would make sense to use Realm? What are the pro and cons?
We are going to use GraphQL and we want to host them where our db is gonna be.
Blog Posts
+5Firebase's Features
- Add the Firebase library to your app and get access to a shared data structure. Any changes made to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.
- Firebase apps can be written entirely with client-side code, update in real-time out-of-the-box, interoperate well with existing services, scale automatically, and provide strong data security.
- Data Accessibility- Data is stored as JSON in Firebase. Every piece of data has its own URL which can be used in Firebase's client libraries and as a REST endpoint. These URLs can also be entered into a browser to view the data and watch it update in real-time.
- Real-time Synchronization- Firebase takes a new approach to the way data is moved around an app. Rather than using a traditional request & response model, it works by synchronizing data between devices. Whenever your data changes, all clients are immediately notified within milliseconds. The synchronized data is also persisted, allowing new clients to be immediately updated.
- First-class Data Security- Traditional applications intermix security code with application code, whereas Firebase treats security as a first-class feature. You define your security policies in one place using a flexible rules language, and Firebase ensures that they are consistently enforced across all parts of your application. Having all your security logic in one place allows for easy auditing and helps you avoid security mistakes. The safety and security of your data is our top priority.
- Automatic Scaling- The Firebase API is built from the ground up for performance and scale. Whenever your data changes, Firebase calculates the minimum set of updates required to keep all your clients in sync. In addition, all Firebase API functions are designed to scale linearly with the size of the data being synchronized. More importantly, Firebase handles all of the scaling and operations for you. Your app will scale from its first user to its first million without any code changes.
- Servers are Optional- Firebase can provide all of the data storage, control, and transmission needs of most apps. In many cases, Firebase can completely replace your server and server-side code. This means you no longer need to build complicated backend software and can instead focus on your application logic and your customers.
