Become a cloud pro with hands-on experience in developing, styling, and managing a Cloud-Native web application using Tailwind, Google Cloud, and Firebase. No setup, no cleanup, no hassle.

Cloud Native Web Development - A Hands-On Guidebook-01.jpg

cloud-native-web-app.tar.gz

username

email

access_token

repository_name

author

firebase_proj_name

FIREBASE_TOKEN

cypress_key

cypress_projectID

dev_api_key

sapper

add-firebase-sdk

install-firebase-cli

cypress-cli

headless-mode

headless-mode-2

component-tests-1

component-tests-2

testing-library

cypress-dashboard

enable-tests-CI

enable-PR

svelte-intro

tailwindcss-component

tailwindcss-svelte

tailwindcss-svelte2

user-auth1

login-page

admin-page

user-svelte-store

signin-vs-signout

secure-admin-page

redirect

configure-firestore

create-user-interface-1

write-data-1

persist-new-blog-1

read-data-1

security-rules

configure-emulator

test-fcf-locally

new-service-placeholder

dev-integration

test-new-service

markdown2html

write-test-for-service-1

deploy-service-req-one

deploy-service-req-two

speed-up-CI-CD

local-dev

emulator-start

ch-2/lesson-5

ch-3/lesson-3

ch-1/lesson-4

ch-3/lesson-4

ch-3/lesson-5

ch-3/lesson-6

ch-4/lesson-3

ch-4/lesson-4

ch-5/lesson-1/1

ch-5/lesson-1

ch-6/lesson-2

ch-6/lesson-3

ch-8/lesson-3

ch-8/lesson-4

ch-8/lesson-6

ch-8/lesson-7

ch-8/lesson-8

ch-9/lesson-3

ch-9/lesson-4

ch-9/lesson-5

ch-10/lesson-1

ch-10/lesson-2

ch-10/lesson-3

ch-10/lesson-4

ch-10/lesson-5

ch-11/lesson-2

ch-11/lesson-3

ch-11/lesson-4

ch-11/lesson-5

ch-11/lesson-6

ch-11/lesson-7

create-user-interface-2

create-user-interface-3

create-user-interface-4

write-data-2

write-data-3

persist-new-blog-2

read-data-2

read-data-3

ch-12/lesson-2

ch-12/lesson-3

ch-13/lesson-2

ch-13/lesson-3

ch-13/lesson-4

ch-13/lesson-5

ch-13/lesson-6

ch-13/lesson-7

ch-13/lesson-8

ch-13/lesson-9

new-service-placeholder-copy

write-test-for-service-2

write-test-for-service-3

ch-14/lesson-1

This course is a hands-on guidebook to walk you through the journey to creating your first web application in the cloud.

In this course, you will have hands-on experience in developing, styling, hosting, testing, and efficiently managing a complete Cloud-Native web application. Along with this, you will learn how to make the important decision of choosing a technology or tool for your web application.

By the end of this course, you will have a set of expertise in developing cloud native web applications that will help you throughout your career.

Cloud Native Development with Tailwind, Google Cloud and Firebase

Whether a relational or non-relational database is needed depends on your project
use cases. It is also common to use both for a given project.

 The focus in this course
is on a **non-relational** document database called [Cloud Firestore](https://firebase.google.com/docs/firestore), which is part of the overall [Firebase
development platform](https://firebase.google.com).

# Cloud Firestore

<center style="width:80%; margin:0 auto; text-align:center;">"A NoSQL document database that lets you easily store, sync, and
query data for your mobile and web apps - at a global scale."</center>

Besides availability, performance, and scalability, flexibility is also important. Firestore provides **collections** to group documents - and nested collections for further granularity where necessary.

It comes with two more very powerful features: **database triggers** and **data
synchronization** between devices, even when they are offline.

## Database triggers

Imagine that you have a User collection where you insert a new document when a new user signs up.

Without Firestore, your application code would first persist the user object in the
database and then, if and only if persisting was successful, call an email service to
send a welcome message to the new user.

With Firestore, you can deploy a service to handle events triggered by changes in your database. Now, all that is left to do for your application code is to persist the
user object. Firestore then automatically triggers your other service to send the
welcome email. If the database changes fail, the email service does not get invoked.

This decouples your code, lets you develop, test, and run individual services independently, and therefore greatly increases development velocity.

## Data synchronization

This is a nifty feature that takes care of a lot of application code you would have to
write by yourself if you wanted to synchronize your data across multiple devices, even when they are offline.

Imagine a social media app where users can post pictures. A user is on an airplane and sees the most amazing aurora borealis. They
take out their phone and open your progressive web app that uses Cloud Firestore and the Firebase SDK. They quickly snap a picture, create a new post, and submit it. Once the plane lands and the mobile device connects to the internet, the post will be
synchronized with Cloud Firestore in the cloud, and friends and family of the
traveler can then enjoy the photo.

## Security Rules

Security rules are a very powerful concept to secure your Firestore database. Let's look at an example
we developed earlier in the course, where we created a Firestore Instance.

```javascript
rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /posts/{post} {
      allow read;
      allow write: if request.auth.uid != null;
    }
  }
}
```

What do you think this snippet of security rules does? Take a minute to read it.
In plain English, anyone can read blog posts, but only authenticated users can
create new posts.

It is also important to note that, based on the above security rules, all other database
operations are prohibited and require explicit rules to enable them! They are secure by
default.

# Alternatives

Many alternatives exist, with varying degrees of added features and services, such
as what Firestore provides. There are too many to provide a comprehensive list, but a few popular database
options include (in no particular order): 

* [MySQL](https://www.mysql.com/)
* [PostgreSQL](https://www.postgresql.org/)
* [MongoDB](https://www.mongodb.com/1)
* [Neo4j](https://neo4j.com/)
* [Cassandra](https://cassandra.apache.org/)

# Why choose Firestore?

As a fully managed service, it fits well with the philosophy of this course as outlined earlier. Firestore relies, as much as possible, on managed services provided by cloud providers.

The event-driven nature of how we can execute services based on changes to the
database makes Cloud Firestore very interesting. In a world that is embracing event-driven
architecture more and more, having that capability provided out of the
box is a great start.

# Chapter Overview

In this chapter, we are going to look at three aspects of Firestore:

* Writing data
* Reading data
* Security Rules

There is a lot more to Firestore and its ecosystem than CRUD (create, read, update,
delete) functionality. For example, we will automatically trigger services based on
changes that happen in the database. For now, let's look at the basics to get your
cloud-native web application foundation in good shape to get started on your own
project.

Referring to the [project overview](https://www.educative.io/courses/cloud-native-development/project-overview), the following diagram gives you an idea of where in the architecture this chapter fits in.

 The focus in this course
is on a **non-relational** document database called [Cloud Firestore](https://firebase.google.com/docs/firestore), which is part of the overall [Firebase
development platform](https://firebase.google.com).

# Cloud Firestore

<center>"A NoSQL document database that lets you easily store, sync, and
query data for your mobile and web apps - at a global scale."</center>

Besides availability, performance, and scalability, flexibility is also important. Firestore provides **collections** to group documents - and nested collections for further granularity where necessary.

It comes with two more very powerful features: **database triggers** and **data
synchronization** between devices, even when they are offline.

## Database triggers

Imagine that you have a User collection where you insert a new document when a new user signs up.

Without Firestore, your application code would first persist the user object in the
database and then, if and only if persisting was successful, call an email service to
send a welcome message to the new user.

With Firestore, you can deploy a service to handle events triggered by changes in your database. Now, all that is left to do for your application code is to persist the
user object. Firestore then automatically triggers your other service to send the
welcome email. If the database changes fail, the email service does not get invoked.

This decouples your code, lets you develop, test, and run individual services independently, and therefore greatly increases development velocity.

## Data synchronization

This is a nifty feature that takes care of a lot of application code you would have to
write by yourself if you wanted to synchronize your data across multiple devices, even when they are offline.

Imagine a social media app where users can post pictures. A user is on an airplane and sees the most amazing aurora borealis. They
take out their phone and open your progressive web app that uses Cloud Firestore and the Firebase SDK. They quickly snap a picture, create a new post, and submit it. Once the plane lands and the mobile device connects to the internet, the post will be
synchronized with Cloud Firestore in the cloud, and friends and family of the
traveler can then enjoy the photo.

## Security Rules

Security rules are a very powerful concept to secure your Firestore database. Let's look at an example
we developed earlier in the course, where we created a Firestore Instance.

```javascript
rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /posts/{post} {
      allow read;
      allow write: if request.auth.uid != null;
    }
  }
}
```

What do you think this snippet of security rules does? Take a minute to read it.
In plain English, anyone can read blog posts, but only authenticated users can
create new posts.

It is also important to note that, based on the above security rules, all other database
operations are prohibited and require explicit rules to enable them! They are secure by
default.

# Alternatives

Many alternatives exist, with varying degrees of added features and services, such
as what Firestore provides. There are too many to provide a comprehensive list, but a few popular database
options include (in no particular order): 

* [MySQL](https://www.mysql.com/)
* [PostgreSQL](https://www.postgresql.org/)
* [MongoDB](https://www.mongodb.com/1)
* [Neo4j](https://neo4j.com/)
* [Cassandra](https://cassandra.apache.org/)

# Why choose Firestore?

As a fully managed service, it fits well with the philosophy of this course as outlined earlier. Firestore relies, as much as possible, on managed services provided by cloud providers.

The event-driven nature of how we can execute services based on changes to the
database makes Cloud Firestore very interesting. In a world that is embracing event-driven
architecture more and more, having that capability provided out of the
box is a great start.

# Chapter Overview

In this chapter, we are going to look at three aspects of Firestore:

* Writing data
* Reading data
* Security Rules

There is a lot more to Firestore and its ecosystem than CRUD (create, read, update,
delete) functionality. For example, we will automatically trigger services based on
changes that happen in the database. For now, let's look at the basics to get your
cloud-native web application foundation in good shape to get started on your own
project.

Referring to the [project overview](https://www.educative.io/courses/cloud-native-development/project-overview), the following diagram gives you an idea of where in the architecture this chapter fits in.

Introduction to Cloud Firestore

Introduction

Create a GitHub Project Using Monorepo Template

Set Up Backend Using Sapper Template

Host Your Web App on Firebase

Set Up The Continuous Deployment Pipeline

Local Development

Feature Toggles

Production Monitoring & Rollbacks

Testing

Tailwind CSS

User Authentication

Database - Cloud Firestore

Firebase Local Emulator Suite

Trigger Services Based on Events

Final Tasks

What's Next?

Introduction to Cloud Firestore

Cloud Firestore