What is Firebase?
Who uses Firebase?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Firebase in their tech stack.
For inboxkitten.com, an opensource disposable email service;
We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.
If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...
- <5ms CPU time limit
- Incompatible with express.js
- one script limitation per domain
Limitations our workload is able to conform with (YMMV)
For hosting of static files, we migrated from Firebase to CommonsHost
More details on the trade-off in between both serverless providers is in the article
This time I want to share something different. For those that have read my stack decisions, it's normal to expect some advice on infrastructure or React Native. Lately my mind has been focusing more on product as a experience than what's it made of (anatomy). As a tech leader, I have to worry about things like: are we taking enough time for reviews? Are we improving over time? Are we faster now? Is our code of higher quality?
For all these questions you can add many great recommendations on your pipeline. We use Trello for bug-tracking and project management. We use https://danger.systems/js/ to add checks for linting, type-enforcing and other quality dimensions in our PRs and a great feature from Vercel that let's you previsualize deployments directly in a PR. However it's not easy to measure this improvements over time. For customer matters we have Amplitude or Firebase analytics, but for our internal process? That's a little bit more complicated.
I collaborated recently with some folks in a small startup as an early adopter to create a metrics dashboard for engineers. I tried to add the tool to stackshare.io but still it doesn't appear as one of the options, please take a look on it over product hunt and let us know https://www.producthunt.com/posts/scope-6
Hi, we are looking to create a sports app that collects and displays player stats. It will include team chats with push notifications for upcoming games etc. We are thinking of using the standard MERN stack route with a GraphQL API or a real-time Firebase database. Any advice would be greatly appreciated.
I need advice for object-oriented data analysis. I have exported a collection of users from Firebase to JSON, and I want to analyze it, for example, how many users are females, males, etc. Are there any tools or packages that could help me quickly analyze this data?
I am setting up a content management system (CMS) in Laravel using #GoogleCloudPlatform. This #CMS will have quite a few polymorphic many-to-many relationships (at least 10) and for that reason I am considering whether I should use Firebase or other #NoSQL databases with Laravel.
I know that there is a laravel-firebase package by Kreait which should allow me to use the firebase as database. My question is therefore:
- Are there any drawbacks to using Firebase with Laravel, which I should be aware of?
- Can I possibly use a hybrid model where some data is stored in the SQL database (e.g. user data) while other is stored in Firebase (e.g. the content).
- Or should I just stick to MySQL and create the several polymorphic many-to-many relationships?
- Should I do both and see what works better?
Any advice is appreciated.
I am in the process of building a mobile application and releasing it to the AppStore. Currently, we're in a TestFlight Beta with ~ 1500 users with a front-end only native iOS app. Before releasing it to production, we would like to add the following functionalities:
User email authentication
Being able to store and synchronise individual user's data ( generated while interacting with the app each day -> "user session" ) between various devices
Having user session data ( anonymized ) available for an admin via a visual interface for querying, generating insights
Simple crud interface for remote configs
GDPR requirements ( e.g. workflows for removing or exporting user data, ideally a way to keep the anonymized data too )
Integration with 3rd party services like Mailchimp or Mixpanel ( which we already use, data is sent directly from the app )
Would appreciate any help with finding the right solution for this case given:
Costs (we don't expect large media files storage)
Flexibility to add new features related to the backend in the future
Infra setup and maintenance
What I've been thinking so far was one of: 1. BaaS AWS/Firebase 2. Custom backend with PostgreSQL 3. PaaS of a Realm type (mobile app already uses Realm for local persistence)
- 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.