Restaurantbackend
HOMEGITHUBYouTubeCONTACT
  • RESTAURANT BACKEND
  • NodeJS V/S firebase
  • Project Requirement
  • FIREBASE
    • What is Firebase?
    • Node js v/s firebase
    • Firebase Zip File Structure
    • Video installation Guide
    • Firebase System Requirement
    • How to Run
    • Cloud Config
    • Firebase Config
    • Firebase Deployment
    • Push Notification for Firebase
  • NODEJS
    • Introduction to NodeJS
    • NodeJS Zip File Structure
    • NodeJS System Requirement
    • How to Run NodeJS
    • Project Structure
    • API Config
    • Push Notification for NodeJS
  • Deployment
    • Heroku NodeJS Api
  • CHANGELOG
    • Changelog
  • SOURCE AND CREDITS
    • Source and Credits
  • User Manual -CMS
    • Home
    • Categories
    • Menu Items
    • Orders
    • Table Booking History
    • Coupons
    • Settings
  • Untitled
Powered by GitBook
On this page
  1. FIREBASE

What is Firebase?

Firebase is a Backend-as-a-Service (Baas). It provides developers with a variety of tools and services to help them develop quality apps, grow their user base, and earn profit.

Firebase is a Backend-as-a-Service — BaaS — and next-generation app-development platform on Google Cloud Platform.

Firebase frees developers to focus on crafting fantastic user experiences. You don’t need to manage servers. You don’t need to write APIs. Firebase is your server, and API is your datastore, all written so generically that you can modify it to suit most of the needs. Yeah, you’ll occasionally need to use other bits of the Google Cloud for your advanced applications. Firebase can’t be everything to everybody. But it gets pretty close.

Firebase Pros & Cons

It’s not all roses.

I mean, it’s mostly roses, but watch the thorns.

Pros

  • Email & password, Google, Facebook, and Github authentication

  • Realtime data

  • Ready-made api

  • Built in security at the data node level

  • File storage backed by Google Cloud Storage

  • Static file hosting

  • Treat data as streams to build highly scalable applications

  • Don’t worry about your infrastructure!

Cons

  • Limited query abilities due to Firebase’s data stream model.

  • Traditional relational data models are not applicable to No SQL; therefore, your SQL chops will not transfer.

  • No on-premise installation.

If you are looking to start the quick and easy setup and less server cost then Firebase Backend is best suited to you but if you are looking to expand business in future where you need lots of custom query and logic then better to go with nodeJS Backend.

PreviousProject RequirementNextNode js v/s firebase

Last updated 5 years ago