Menu

Firebase Explained: A Backend Without Building a Backend
πŸ“°

Firebase Explained: A Backend Without Building a Backend

DEV Community: firebaseΒ·The Practical DeveloperΒ·1 day ago
#Qz4JerNe
#devtofirebase#devto#dev#firebase#code
Reading 0:00
15s threshold

Introduction

Building an app usually means building two things: the app people see, and the backend that stores data, handles logins, and serves it all. Firebase, Google's platform launched in 2011 and acquired by Google in 2014, offers the second half as a service: authentication, databases, file storage, hosting, and analytics, all reachable from frontend code with a few lines of setup. For a solo developer or a small team, it can be the difference between shipping in a weekend and spending a month on infrastructure.

What you get in one platform

Firebase is a bundle, and its most-used pieces are:

Authentication β€” email/password, Google, GitHub, and phone sign-in, without writing password storage or session code yourself

Firestore β€” a NoSQL document database (in the same family as the MongoDB post) that syncs data to clients in real time

Hosting β€” static hosting with a global CDN and free SSL, ideal for the frontend of a web app

Cloud Functions β€” small pieces of server code that run on demand, for…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.