ฐานข้อมูลและฟังก์ชันบนคลาวด์

Welcome! Today, we'll explore cloud databases and serverless functions, essential tools for scalable mobile apps. They provide robust, managed backends without the hassle of server maintenance.

We'll focus on Firestore, a popular choice for real-time data, and Cloud Functions for custom backend logic.

Cloud Firestore is a flexible, scalable NoSQL document database. Unlike traditional relational databases with tables and rows, Firestore organizes data into collections and documents.

Each document contains key-value pairs, known as fields. Documents live within collections, and collections can even contain subcollections.

Understanding collections and documents is key to structuring your app's data efficiently. Imagine a simple e-commerce app:

• users (collection)
• user_alice_id (document)
• name: "Alice"
• email: "alice@example.com"
• products (collection)
• product_xyz_id (document)
• name: "Cool Gadget"
• price: 99.99

Adding data to Firestore is straightforward. You can use add() to let Firestore generate a unique document ID, or set() to specify your own ID or overwrite an existing document.

Here's how to add a new user to a 'users' collection:

To retrieve a document or a collection of documents once, you use the get() method. This is useful for data that doesn't require constant, real-time updates.

Let's fetch a specific user's data using their document ID:

Firestore's real-time capabilities are powerful. By using onSnapshot(), you can listen for changes to documents or collections. Whenever data changes on the backend, your app receives instant updates.

This snippet demonstrates listening to a single document for real-time changes:

Cloud Functions are serverless pieces of code that run in response to specific events. They let you execute custom backend logic without needing to manage or provision any servers.

They're perfect for extending your BaaS (like Firebase) with custom features, security rules, or integrations.

Cloud Functions are 'event-driven,' meaning they only run when a specific event occurs. These events are called triggers. Common types include:

• HTTP triggers: For creating API endpoints.
• Firestore triggers: React to document creation, updates, or deletions.
• Authentication triggers: Respond to user sign-ups or deletions.
• Scheduled triggers: Run functions at specific times (e.g., daily cleanup).

Let's create a simple Cloud Function that responds to an HTTP request. This is like building a tiny, serverless API endpoint. It's a great way to handle custom logic that your mobile app might need.

This example will return a basic "Hello from Firebase!" message.

Cloud Functions and Firestore are a powerful combination. Functions can automatically react to changes in your Firestore database, allowing you to:

• Update aggregate counts (e.g., total likes on a post).
• Perform data validation or sanitization.
• Send notifications or emails after a user action.

This keeps your app's logic robust and efficient, handling backend tasks seamlessly.

You've explored the core concepts of Cloud Firestore for scalable, real-time data storage using a flexible NoSQL document model. You also learned about Cloud Functions, which enable you to deploy serverless backend logic in response to various triggers.

Mastering these tools is fundamental for building dynamic, robust, and efficient indie mobile apps!