JobCannon
全部技能

Firestore Real-Time

⬢ 層級 2技術
中等
薪資影響
2 個月
學習時長
中等
難度
12
職業
一覽

Firestore (Cloud Firestore) is Google's NoSQL database optimized for real-time and serverless. Unlike Realtime DB (JSON tree), Firestore has proper collections, documents, queries (filter by any field), transactions, and 5-region replication. Real-time listeners sync data across clients. Practitioners use Firestore for most production apps (e-commerce, SaaS, social). Learning: 2-3 weeks for CRUD, 6-8 weeks for advanced patterns (denormalization, fan-out writes). Specialists earn 15-20% premium for architecting scalable data models. Firestore is the modern choice; 80% of new Firebase projects use Firestore.

什麼是 Firestore Real-Time

Firestore (Cloud Firestore) is Google's modern NoSQL database. It stores data in collections (tables) and documents (rows as JSON). Real-time listeners sync data across all connected clients via WebSockets. Supports rich queries (filter, sort, paginate on any field), transactions (atomic multi-document updates), and multi-region replication (data replicated across 5 regions for redundancy). Unlike traditional databases, Firestore scales automatically: 1 user or 1M users, same code. No ops teams needed. Works offline (queues changes, syncs when online).

🔧 工具與生態
Cloud FirestoreFirebase SDK (iOS, Android, Web)Real-time listenersFirestore queries and indexesSecurity RulesTransactions and batchesCloud Functions integration

💰 各地區薪資

地區初級中級高級
USA$80,000$130,000$190,000
UK£46,000£76,000£115,000
EU€52,000€85,000€130,000
CANADACA$85,000CA$140,000CA$205,000

❓ 常見問題

When should I use Firestore vs MongoDB?
Firestore: small-medium projects, serverless, want real-time, Google ecosystem. MongoDB: complex queries, sharding, self-hosted, larger scale. For startups: Firestore. For enterprises: MongoDB Atlas or self-hosted.
What's Firestore Datastore vs Firestore in native mode?
Native mode: real-time, better for mobile/web. Datastore mode: better for large-scale OLTP, less real-time. Start with native mode; switch to Datastore if you hit scale limits.
How do you handle relationships in Firestore?
Two approaches: (1) Reference: store document ID, fetch separately (normalized). (2) Denormalize: embed related data in document. Denormalize for frequently accessed data; reference for infrequent.
What's a subcollection and when should I use it?
Subcollection: nested collection within a document. Example: users/{uid}/posts/{postId}. Use for one-to-many relationships. Avoid deep nesting (slow).
How do transactions work in Firestore?
Read multiple documents, compute, write results atomically. Example: transfer money (debit account A, credit account B). Both succeed or both fail (no partial updates).

不確定這項技能適不適合你？

做一下職業匹配，我們會推薦合適的方向。

找到最適合我的技能 →

找到理想的職業方向

在 2,521 個職業中進行技能匹配。免費。

免費做職業匹配 →