mirror of
https://github.com/ByteByteGoHq/system-design-101.git
synced 2026-04-01 16:57:23 -04:00
ee4b7305a2
This PR adds all the guides from [Visual Guides](https://bytebytego.com/guides/) section on bytebytego to the repository with proper links. - [x] Markdown files for guides and categories are placed inside `data/guides` and `data/categories` - [x] Guide links in readme are auto-generated using `scripts/readme.ts`. Everytime you run the script `npm run update-readme`, it reads the categories and guides from the above mentioned folders, generate production links for guides and categories and populate the table of content in the readme. This ensures that any future guides and categories will automatically get added to the readme. - [x] Sorting inside the readme matches the actual category and guides sorting on production
39 lines
1.5 KiB
Markdown
39 lines
1.5 KiB
Markdown
---
|
|
title: "What is Cloud Native?"
|
|
description: "Explore cloud native technologies and their impact on application architecture."
|
|
image: "https://assets.bytebytego.com/diagrams/0413-what-is-cloud-native.png"
|
|
createdAt: "2024-03-12"
|
|
draft: false
|
|
categories:
|
|
- cloud-distributed-systems
|
|
tags:
|
|
- Cloud Computing
|
|
- Microservices
|
|
---
|
|
|
|
Below is a diagram showing the evolution of architecture and processes since the 1980s.
|
|
|
|
|
|
|
|
Organizations can build and run scalable applications on public, private, and hybrid clouds using cloud native technologies.
|
|
|
|
This means the applications are designed to leverage cloud features, so they are resilient to load and easy to scale.
|
|
|
|
Cloud native includes 4 aspects:
|
|
|
|
* **Development process**
|
|
|
|
This has progressed from waterfall to agile to DevOps.
|
|
|
|
* **Application Architecture**
|
|
|
|
The architecture has gone from monolithic to microservices. Each service is designed to be small, and adaptive to the limited resources in cloud containers.
|
|
|
|
* **Deployment & packaging**
|
|
|
|
The applications used to be deployed on physical servers. Then around 2000, the applications that were not sensitive to latency were usually deployed on virtual servers. With cloud native applications, they are packaged into docker images and deployed in containers.
|
|
|
|
* **Application infrastructure**
|
|
|
|
The applications are massively deployed on cloud infrastructure instead of self-hosted servers.
|