What’s new in Firestore from Cloud Next and Firebase Summit 2022

Developers love Firestore because of how fast they can build an application end to end. Over 4 million databases have been created in Firestore, and Firestore applications power more than 1 billion monthly active end users using Firebase Auth. We want to ensure developers can focus on productivity and enhanced developer experience, especially when their apps are experiencing hyper-growth. To achieve this, we’ve made updates to Firestore that are all aimed at developer experience, supporting growth and reducing costs.

COUNT function

We’ve rolled out the COUNT() function, which gives you the ability to perform cost-efficient, scalable, count aggregations. This capability supports use cases like counting the number of friends a user has, or determining the number of documents in a collection. 

For more information, check out our Powering up Firestore to COUNT() cost-efficiently blog.

Query Builder and Table View

We’ve rolled out Query Builder to enable users to visually construct queries directly in the console across Google Cloud and Firebase platforms. The results are also shown in a table format to enable deeper data exploration.

For more information, check out our Query Builder blog.

Scalable backend-as-a-service (BaaS)

Firestore BaaS has always been able to scale to millions of concurrent users consuming data with real time queries, but up until now, there has been a limit of 10,000 write operations per second per database. While this is plenty for most applications, we are happy to announce that we are now removing this limit and moving to a model where the system scales up automatically as your write traffic increases.

For applications using Firestore as a backend-as-a-service, we've removed the limits for write throughput and concurrent active connections. As your app takes off with more users, you can be confident that Firestore will scale smoothly. 

For more information, check out our  Building Scalable Real Time Applications with Firestore blog.

Time-to-live

To help you efficiently manage storage costs, we’ve introduced time-to-live (TTL), which enables you to pre-specify when documents should expire, and rely on Firestore to automatically delete expired documents.

For more information, check out our blog: Manage Storage Costs Using Time-to-Live in Firestore

Additional Features for Performance and Developer Experience

In addition, the following features have been added to further improve performance and developer experience:

Tags have been added to enable developers to tag databases, along with other Google Cloud resources, to apply policy and observer group billing.

Cross-service security rules allow secure sharing of Cloud Storage objects, by referencing Firestore data in Cloud Storage Security Rules.

Offline query (client-side) indexing ^Preview enables more performant client-side queries by indexing data stored in the web and mobile cache.  Read documentation for more information.

What’s next

Get started with Firestore.