Application and Data / Application Hosting / Realtime Backend / API
Avatar of johnnyxbell
Senior Software Engineer at StackShare·

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

71 upvotes·9 comments·787.4K views

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools


10 upvotes·1 comment·1.3M views
Avatar of jsdario
Telecomm Engineering at Netbeast·

We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

Developing beyond the screen – React Native Development – Medium (
10 upvotes·707K views
Avatar of jwuliger
Contractor at Insight Global·

I started using Firebase over 5 years ago because of the 'real-time' nature. I originally used to use Real Time Database, but now I use Cloud Firestore. I recommend using the Google Firebase PaaS to quickly develop or prototype small to enterprise level web/mobile applications. Since Google purchased Firebase, it has exploded and it growing rapidly. I also find some level of comfort that it is Backed by Google.

9 upvotes·1 comment·244.7K views
Avatar of PicoCreator
CTO at Uilicious·

For, 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 ...

  1. <5ms CPU time limit
  2. Incompatible with express.js
  3. 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

Why we migrated opensource 😼inboxkitten (77 million serverless request) from 🔥Firebase to ☁️Cloudflare workers & 🐑CommonsHost - DEV Community 👩‍💻👨‍💻 (
8 upvotes·14.8K views
Avatar of nowaq
Co-founder at Evojam·

In a couple of recent projects we had an opportunity to try out the new Serverless approach to building web applications. It wasn't necessarily a question if we should use any particular vendor but rather "if" we can consider serverless a viable option for building apps. Obviously our goal was also to get a feel for this technology and gain some hands-on experience.

We did consider AWS Lambda, Firebase from Google as well as Azure Functions. Eventually we went with AWS Lambdas.

  • No servers to manage (obviously!)
  • Limited fixed costs – you pay only for used time
  • Automated scaling and balancing
  • Automatic failover (or, at this level of abstraction, no failover problem at all)
  • Security easier to provide and audit
  • Low overhead at the start (with the certain level of knowledge)
  • Short time to market
  • Easy handover - deployment coupled with code
  • Perfect choice for lean startups with fast-paced iterations
  • Augmentation for the classic cloud, server(full) approach
  • Not much know-how and best practices available about structuring the code and projects on the market
  • Not suitable for complex business logic due to the risk of producing highly coupled code
  • Cost difficult to estimate (helpful tools:
  • Difficulty in migration to other platforms (Vendor lock⚠️)
  • Little engineers with experience in serverless on the job market
  • Steep learning curve for engineers without any cloud experience

More details are on our blog: I hope it helps 🙌 & I'm curious of your experiences.

Should You go Serverless? Meet The Benefits And Flaws of New Wave of Cloud Solutions — Evojam (
7 upvotes·1 comment·374.8K views
Avatar of timbergus
Web UI Developer at Globant·
Shared insights

Considering myself an 80%/20% full-stack, my time using Node.js at the backend is limited. This is why I have started using Firebase as the back for most of my personal applications. The amount of tools and resources is amazing and covers the most common needs like #authentication, storage, database, real-time database, actions, and hosting. It's a total grown-up product and the free tier is enough for most of my personal projects.

7 upvotes·251.1K views
Needs advice

I'm planning to make a web app with browser games that would be a Progressive Web App. I decided to use Vue.js as the front framework and Firebase to store basic information about users. Then I found out about Nuxt.js and I figured it could be really handy for making the project as PWA.

The thing is, that I don't know if I will need Server Side Rendering for this, I couldn't find a lot of information but from what I know, the web app doesn't need SSR to be PWA. I am not sure how this would work with JavaScript browser games made with frameworks like Phaser or melon.js. Also, I host my website on GoDaddy and I've heard that it's quite hard to set up SSR with cPanel.

So my questions are:

Should I use SSR for Progressive Web Application built with Nuxt, filled with javascript browser games that are lazily loaded, or does that not make sense? If it makes sense, would SSR work with godaddy hosting and cPanel?

Any help would be appreciated!

7 upvotes·24.9K views
Replies (1)

Perhaps you could generate static website with Nuxt and deploy on cPanel or some free static hosting.

6 upvotes·1 view

Fontumi focuses on the development of telecommunications solutions. We have opted for technologies that allow agile development and great scalability.

Firebase and Node.js + FeathersJS are technologies that we have used on the server side. Vue.js is our main framework for clients.

Our latest products launched have been focused on the integration of AI systems for enriched conversations. Google Compute Engine , along with Dialogflow and Cloud Firestore have been important tools for this work.

Git + GitHub + Visual Studio Code is a killer stack.

6 upvotes·1 comment·688.6K views
Avatar of lucazin
CEO & Founder at ¹OnePlace·

At the beginning of the ¹OnePlace project, our team needed to decide which service to use to send bulk notifications to all users quickly and consistently. We tested some services without success and as we already used firebase we decided to implement in the beginning using Notifications by Firebase. We're having trouble updating the user's token to see if it has removed the app or not. This brought a working overhead and we were not sure if the notification had arrived at the destination. Today we use OneSignal, which did not bring reliability to the submitted notifications, nor do we need to bother with manual token updates. We ship approximately 500 thousand notifications with 100% delivery!

OneSignal Firebase

6 upvotes·258.5K views