Google Cloud has announced a major transformation to Firestore, its serverless NoSQL document database used by millions of developers worldwide. Now, users can operate and manage multiple Firestore databases within a single project. This cutting-edge feature has immense potential as it accommodates the creation and administration of an unlimited number of databases in one place. The system simplifies isolation of customer data, microservices, and separates development, test, and staging environments much more effectively.
The new Firestore update introduces a wide range of features that specifically aid in managing database operations efficiently. Notably, Firestore has unveiled fresh API endpoints, Terraform resources, and CLI commands for both gcloud and Firebase. These are powerful tools designed to manage more than one Firestore database.
The update also marks the inception of a dynamic security management system- the IAM Conditions, or Firebase Security Rules, that allow different security policies to be implemented on different Firestore databases. Furthermore, users can now set up databases in the same project in either Firestore’s datastore mode or native mode. The choice is theirs!
The innovative feature extends across Google’s global footprint of Firestore regions, allowing new databases to be created in any Firebase project region. Furthermore, billing for each database can be tracked individually via Cloud Billing and BigQuery, making expenditure more transparent and manageable. Not to be missed is Firestore’s Cloud Monitoring capabilities which have been enhanced with metrics now aggregated at the database level.
Firestore’s potential value is best understood through practical application. For example, to create a Firestore database, one simply specifies the database identifier, mode, and location. Google cloud CLI, amongst various tools, can be used to create a Firestore database. Application of CLI commands can create, access, and delete a Firestore database.
Integrating Firestore client libraries with your databases is a simplified process aimed at efficiency. For example, writing to a specified database in Java is a straightforward operation. Do remember, database names need to be specified when using Firestore client libraries; otherwise, the original (default) database will be used.
In conclusion, the new feature unveiled by Google Cloud promises to revolutionize Firestore by providing the ability to manage multiple databases within a single project. It is a strong example of how Google continues to invest in rapid innovation to improve efficiency and provide flexible solutions for developers. For detailed setup instructions and configurations, the Google documentation on Firestore databases support is an excellent resource.
Google Cloud’s recent Firestore update is a powerful leap forward for multiple databases, Firestore database operations, access control, security policies, native and datastore modes, Cloud Monitoring, billing, and Firestore Client Libraries. The flexibility and functionality that it brings to a single project is truly unparalleled. With this feature, Google Cloud strengthens its commitment to providing progressive, user-friendly, and advanced database management tools to developers around the globe.
Up until working with Casey, we had only had poor to mediocre experiences outsourcing work to agencies. Casey & the team at CJ&CO are the exception to the rule.
Communication was beyond great, his understanding of our vision was phenomenal, and instead of needing babysitting like the other agencies we worked with, he was not only completely dependable but also gave us sound suggestions on how to get better results, at the risk of us not needing him for the initial job we requested (absolute gem).
This has truly been the first time we worked with someone outside of our business that quickly grasped our vision, and that I could completely forget about and would still deliver above expectations.
I honestly can't wait to work in many more projects together!
![The ‘Giveaway Piggy Back Scam’ In Full Swing [2022]](https://www.cjco.com.au/wp-content/uploads/pexels-nataliya-vaitkevich-7172791-1-scaled-2-683x1024.jpg)
Disclaimer
*The information this blog provides is for general informational purposes only and is not intended as financial or professional advice. The information may not reflect current developments and may be changed or updated without notice. Any opinions expressed on this blog are the author’s own and do not necessarily reflect the views of the author’s employer or any other organization. You should not act or rely on any information contained in this blog without first seeking the advice of a professional. No representation or warranty, express or implied, is made as to the accuracy or completeness of the information contained in this blog. The author and affiliated parties assume no liability for any errors or omissions.
