PWIFE-539
## [**Cloud Firestore Database**] by Google
Cloud Firestore is a NoSQL database built for mobile, web, and server applications from Google. It supports server, real-time, and offline data synchronization. Cloud Firestore can scale to help us build datasets for an on-demand app. It also supports sophisticated queries and complex transactions.
### **Features Of Cloud Firestore**
• Speed and scalability: Cloud Firestore can scale to help our web, mobile, and server applications with data storage. It can support thousands of simultaneous connections, even when working offline.
• Offline support: Cloud Firestore can work offline, even when the connection is disrupted. It will work the next time the user connects online.
• Visibility and analytics: Cloud Firestore can track and observe the system's usage and performance. It gives us information on user activity and performance metrics.
• Data synchronization: Cloud Fire is a real-time database that can sync data across all devices that can be used by users. It can even sync data with other websites like Firebase, Push, etc.
• **Documentation and support**: Cloud Firestore has documentation that provides an overview and key details about the features and principle of operation. It helps developers get started with the process.
### **Pros Of Cloud Firestore**
• Provides easy and structured basic data: The Service is easy to use and provides a structured basis for clients to start their development pace.
• Scaling and monitoring made easy: Users can scale the service to support their platform. They can also gain insight on the performance and operation through monitoring.
• Real-time data synchronization: The Service can synchronize data in real-time with other users.
• **Offline support**: Users can use the Service offline without the need for live connectivity.
•
### **Cons Of Cloud Firestore**
• Limited features: The Service has limited features in its base package that are insufficient for some uses. Theme editors have to add additional features to meet the requirements.
• Lack of visibility and transparency: The Service lacks the capability to track and monitor system activities. Isolate technical faults are also harder to observe and locate.
• Costs fluctuate with the scalability: The Service might not be cost-effective for businesses that need constant connection.
• Additional FILE per file: Although the Service has a free rate, users are charged every time they process a file.
### **Tutorial**
**Step 1:** Install the required dependencies
Get the installation file. You can access the file on the database's website or with the provided command in the designated terminal. > npm install cloud-firestore
Dependencies are necessary for the Database to work correctly. Avoid errors by repeating this step when installing dependencies for other functions.
**Step 2:** Configure the initial project file
Let’s initialize the configuration rules for DataStore almost in step1. You can create the file on your local device or the terminal. Either way will sync file storage.
Remember to sync the cloud Firestore twice. First, index the source and source, and then reindex the second time.
**Step 3:** Reload the database to examine the rule you made
The process will ask for the access token. Select the checkbox to approve the query. Then, click on the button to establish the connection.
**Step 4:** Confirm the database updated correctly
If the pull succeeds, you’ll get a notification in the terminal. Try a few times to confirm the database still works correctly.
**Step 5:** Add details to Firestore database
Specify the entities into that database. Block entities you can use for the development process. Export entities to database synchronizations, press the Generate button.
**Step 6:** Save new values in the database
Save the new values in the database. Once loaded, relaunch the database to the correct the service status.
**Step 7:** Make changes in the database
Query those items to make the desired changes in the database. Select the content to overwrite with the new data. That’ll make changes in the database permanently.
**Step 8:** Use the database to synchronize values
Add account values to the database. Replace the initial values and make the operating shared ownership. That’ll make the data organized and persistent.
**Step 9:** Save the database status
If you’re finished, make sure to save the database. Configure the values and save the final execution in the database for saving device data.
**Step 7:** Make changes in the database
Query these items to make the desired changes in the database. Select the content to overwrite with the new data. That’ll make changes in the database permanently.
**Step 8:** Use the database to synchronize values
Add account values to the database. Replace the initial values and make the operating shared ownership. That’ll make the data structured and persistent.
**Step 9:** Save the database status
If you’re finished, make sure to save the database. Configure the values and save the final execution in the database for saving device data.
............
### **Challenges**
### **Onboarding for beginners**
Users may run into conflicts when setting up system configuration. Prevent problems by copying and pasting safe operational values to secure their stances.
*Targeting these difficult tasks, limit and create strong passwords. Protect the headgear by performing both the initial login and the first connection validation.
### **Takeover and scaling**
Users have to think through scaling before capacity starts. In the event of a pull failure, in the worst case scenario, the database can stop functioning immediately. The user experience must be negatively influenced if things go wrong.
### **Preview**
2019年4月21日
英語字幕
中国語字幕
日本語字幕
フランス語字幕
