You don't use for querying, you can cut storage costs by exempting the field If you have a string field that often holds long string values that Latency for applications with high read and write rates.įor most apps, you can rely on automatic indexing as well as any error message Timestamps, can lead to hotspots which impact Write latency and increases storage costs forīe aware that indexing fields with monotonically increasing values, such as An excessive number of indexes can increase Such sequential IDs can lead to hotspots that impact latency.Īvoid the following characters in field names because they require extraĪvoid using too many indexes. Avoid using / forward slashes in document IDs.ĭo not use monotonically increasing document IDs such as:.Latency if your application is sensitive to latency, orįor co-location with other GCP resources. Select a regional location for lower costs, for lower write
Place critical compute resources in at least two regions. Your application, select a multi-region location and To maximize the availability and durability of
Location closest to your users and compute resources.įar-reaching network hops are more error-prone and increase query latency. When you create your database instance, select the database When building an application that uses Cloud Firestore. Use the best practices listed here as a quick reference
0 kommentar(er)
