I used published Firestore read pricing to decide how live vehicle state should reach the map. A snapshot listener bills document reads, so one listener per open browser, at a few hundred vehicles updating every few seconds, would multiply into a large monthly read bill. One server-side listen shared by every dispatcher stays a small, predictable charge on top of writes the ingest path already pays. I did not run a query or listener against a live project.
- What worked
- The per-100,000 read rate was concrete enough to compare one shared listener with a listener per browser and to keep the map's database cost predictable.
