Firebase Realtime Database Cheat Sheet

Updated 2026-04-29

Next Topic: Graph Databases Landscape and Comparison Cheat Sheet

🧠Study flashcards on this topic95 cards · spaced repetition→

Firebase Realtime Database is Google's cloud-hosted NoSQL database that stores data as JSON and synchronizes it in real-time across all connected clients—typically within milliseconds. Unlike traditional databases requiring HTTP polling, it uses WebSocket-based data synchronization where every write instantly pushes updates to all listening devices, making it ideal for collaborative apps, chat systems, and live dashboards. Data persists locally during offline periods and automatically syncs when connectivity returns, merging conflicts server-side. A key design principle: flatten your data structure aggressively—because fetching a node retrieves all child data, deeply nested trees force massive downloads and break granular security rules, so denormalization (duplicating data across paths) is the norm, not the exception.

What This Cheat Sheet Covers

This topic spans 19 focused tables and 142 indexed concepts, 95 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: SDK Initialization & SetupTable 2: Core Write OperationsTable 3: Read & Listener PatternsTable 4: DataSnapshot MethodsTable 5: Query & Sort OperationsTable 6: Data Structure PatternsTable 7: Security Rules SyntaxTable 8: Offline CapabilitiesTable 9: Server Values & TimestampsTable 10: REST API OperationsTable 11: Admin SDK OperationsTable 12: Local Emulator SuiteTable 13: Cloud Functions TriggersTable 14: Authentication IntegrationTable 15: Performance OptimizationTable 16: Pricing & LimitsTable 17: Data Types & LimitationsTable 18: Common GotchasTable 19: Comparison to Cloud Firestore

Quick IndexSubscribe to unlock

A jump-to index of every table row in this cheat sheet.

Mind MapSubscribe to unlock

An interactive map of every table and concept in this topic.

Table 1: SDK Initialization & Setup

Every Firebase app starts here—wiring up the SDK, pointing it at your database, and grabbing references to the JSON paths you'll read and write. The databaseURL format varies by region, and connecting to the local emulator is a one-liner you slot in right after getDatabase().

Method	Example	Description
initializeApp()	`import { initializeApp } from "firebase/app"` `const app = initializeApp({ databaseURL: "https://NAME.firebaseio.com" })`	• Initializes the Firebase app with your project config • `databaseURL` is required for RTDB.
getDatabase()	`import { getDatabase } from "firebase/database"` `const db = getDatabase(app)`	• Returns the database service instance • pass `app` explicitly when using multiple Firebase apps.
ref()	`import { ref } from "firebase/database"` `const usersRef = ref(db, 'users/123')`	• Creates a database reference to a specific path • root reference: `ref(db)` with no path.
child()	`const nameRef = child(usersRef, 'profile/name')`	Returns a child reference relative to an existing reference without triggering any read.
Database URL format	`https://NAME.firebaseio.com` (us-central1) `https://NAME.REGION.firebasedatabase.app` (other regions)	• The URL format depends on the database region • all other regions use the regional suffix.
connectDatabaseEmulator()	`connectDatabaseEmulator(db, "127.0.0.1", 9000)`	• Redirects all SDK calls to the local RTDB emulator • call this immediately after `getDatabase()`, before any reads or writes.

Table 2: Core Write Operations

The four ways to get data into the tree—plus the two atomic primitives that keep concurrent writes honest. The key distinction to internalize: set() clobbers everything at a path while update() merges only the fields you name, and push() mints a time-ordered key so lists stay ordered without a counter.

Method	Example	Description
set()	`set(ref(db, 'users/123'), {name: 'Ada', age: 36})`	Overwrites all data at the path, removing existing children not in the new object.

The rest of this section is part of the full cheat sheet

Table 3: Read & Listener Patterns

This is where the "realtime" lives. Attach a listener and your callback fires once with current data, then again on every change—or use get() for a one-shot read with no subscription. The child-level events (onChildAdded, onChildChanged, onChildRemoved, onChildMoved) let you react to individual list items instead of re-rendering whole nodes, and off() is the cleanup you must not forget.

Method	Example	Description
onValue()	`onValue(ref(db, 'status'), (snap) => {` `console.log(snap.val())` `})`	Fires once with current data on attach, then on every change to the node or descendants.

The rest of this section is part of the full cheat sheet

Table 4: DataSnapshot Methods

Reads and listeners hand you a snapshot, not raw data—these are the methods for unpacking it. .val() extracts the JavaScript value, .exists() and .hasChild() answer existence questions without materializing data, and .forEach() walks children in query sort order, which a plain Object.keys() loop would not preserve.

Method	Example	Description
.val()	`snap.val()`	Extracts the snapshot's data as a JavaScript value (object, array, string, number, boolean, or `null` if empty).

The rest of this section is part of the full cheat sheet

Table 1: SDK Initialization & Setup

Method	Example	Description
initializeApp()	`import { initializeApp } from "firebase/app"` `const app = initializeApp({ databaseURL: "https://NAME.firebaseio.com" })`	• Initializes the Firebase app with your project config • `databaseURL` is required for RTDB.
getDatabase()	`import { getDatabase } from "firebase/database"` `const db = getDatabase(app)`	• Returns the database service instance • pass `app` explicitly when using multiple Firebase apps.
ref()	`import { ref } from "firebase/database"` `const usersRef = ref(db, 'users/123')`	• Creates a database reference to a specific path • root reference: `ref(db)` with no path.
child()	`const nameRef = child(usersRef, 'profile/name')`	Returns a child reference relative to an existing reference without triggering any read.
Database URL format	`https://NAME.firebaseio.com` (us-central1) `https://NAME.REGION.firebasedatabase.app` (other regions)	• The URL format depends on the database region • all other regions use the regional suffix.
connectDatabaseEmulator()	`connectDatabaseEmulator(db, "127.0.0.1", 9000)`	• Redirects all SDK calls to the local RTDB emulator • call this immediately after `getDatabase()`, before any reads or writes.

Table 2: Core Write Operations

Method	Example	Description
set()	`set(ref(db, 'users/123'), {name: 'Ada', age: 36})`	Overwrites all data at the path, removing existing children not in the new object.

Table 3: Read & Listener Patterns

Method	Example	Description
onValue()	`onValue(ref(db, 'status'), (snap) => {` `console.log(snap.val())` `})`	Fires once with current data on attach, then on every change to the node or descendants.

Table 4: DataSnapshot Methods

Method	Example	Description
.val()	`snap.val()`	Extracts the snapshot's data as a JavaScript value (object, array, string, number, boolean, or `null` if empty).