From 61744caf59fc532e95c56deee5f55c2286341e4a Mon Sep 17 00:00:00 2001 From: joseeden Date: Sun, 7 Jan 2024 17:42:45 +0800 Subject: [PATCH] Added link to main page, for cloudnative sections. --- pages/03-Cloud-Native/001-What-is-Cloud-Native.md | 4 +++- .../002-Containers-and-being-Cloud-Native.md | 5 +++++ pages/03-Cloud-Native/003-Cloud-Native-Landscape.md | 5 +++++ .../004-Business-and-Technical-Considerations.md | 6 ++++++ pages/03-Cloud-Native/005-Design-Considerations.md | 7 ++++++- pages/03-Cloud-Native/006-Monoliths-and-Microservices.md | 5 +++++ pages/03-Cloud-Native/007-Tradeoffs.md | 5 +++++ .../008-Best-Practice-for-App-Deployments.md | 7 ++++++- .../03-Cloud-Native/009-Product-is-Released-Whats-Next.md | 5 +++++ 9 files changed, 46 insertions(+), 3 deletions(-) diff --git a/pages/03-Cloud-Native/001-What-is-Cloud-Native.md b/pages/03-Cloud-Native/001-What-is-Cloud-Native.md index f6f5505..50e9faa 100755 --- a/pages/03-Cloud-Native/001-What-is-Cloud-Native.md +++ b/pages/03-Cloud-Native/001-What-is-Cloud-Native.md @@ -26,4 +26,6 @@ We'll get to explore how microservices ties in with Cloud-native in the labs. -[Back to first page](../../README.md##cloud-native) \ No newline at end of file +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/002-Containers-and-being-Cloud-Native.md b/pages/03-Cloud-Native/002-Containers-and-being-Cloud-Native.md index 4b6ddb8..b2cf002 100755 --- a/pages/03-Cloud-Native/002-Containers-and-being-Cloud-Native.md +++ b/pages/03-Cloud-Native/002-Containers-and-being-Cloud-Native.md @@ -14,3 +14,8 @@ The third key thing is **containers**. To recall, containers are simply **processes** which wraps the dependencies and libraries so that it can be shipped as runnable applications across different platforms. They are closely associated with cloud native applications as containers are a great way to deploy applications quickly and resiliently given their lightweight feature. + + +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/003-Cloud-Native-Landscape.md b/pages/03-Cloud-Native/003-Cloud-Native-Landscape.md index 8069138..7370c3c 100755 --- a/pages/03-Cloud-Native/003-Cloud-Native-Landscape.md +++ b/pages/03-Cloud-Native/003-Cloud-Native-Landscape.md @@ -27,3 +27,8 @@ Over time, Kubernetes was developed to include more than just automation but als - Service Mesh - Logs and metrics - Tracing + + +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/004-Business-and-Technical-Considerations.md b/pages/03-Cloud-Native/004-Business-and-Technical-Considerations.md index 568a051..2575e69 100755 --- a/pages/03-Cloud-Native/004-Business-and-Technical-Considerations.md +++ b/pages/03-Cloud-Native/004-Business-and-Technical-Considerations.md @@ -13,3 +13,9 @@ From a technical perspective, the adoption of cloud-native tooling represents: - **Automation** - release a service without human intervention - **Orchestration** - introduce a container orchestrator to manage thousands of services with minimal effort - **Observability** - ability to independently troubleshoot and debug each component + + +
+ +[Back to first page](../../README.md##cloud-native) + diff --git a/pages/03-Cloud-Native/005-Design-Considerations.md b/pages/03-Cloud-Native/005-Design-Considerations.md index 423edec..986a871 100755 --- a/pages/03-Cloud-Native/005-Design-Considerations.md +++ b/pages/03-Cloud-Native/005-Design-Considerations.md @@ -16,4 +16,9 @@ It is necessary to allocate time at the start to identifying the design factors Here we determine what is the context of implementing these functionalities. - Engineering resources - *Who can work on the project?* - Financial resources - *How much is the budget?* - - Timeframes - *How soon do we want the project to finish?* \ No newline at end of file + - Timeframes - *How soon do we want the project to finish?* + + +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/006-Monoliths-and-Microservices.md b/pages/03-Cloud-Native/006-Monoliths-and-Microservices.md index 7a8be6d..f2cb334 100755 --- a/pages/03-Cloud-Native/006-Monoliths-and-Microservices.md +++ b/pages/03-Cloud-Native/006-Monoliths-and-Microservices.md @@ -51,3 +51,8 @@ In a microservice architecture, application tiers can be described as The main point of microservices is to break the software into smaller chunks, allowing developers to work on a piece of the code and release on their own cycle, which in turn speeds up development. This kind of architecture also enables the software to scale independently. + + +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/007-Tradeoffs.md b/pages/03-Cloud-Native/007-Tradeoffs.md index b3d1725..dc3538f 100755 --- a/pages/03-Cloud-Native/007-Tradeoffs.md +++ b/pages/03-Cloud-Native/007-Tradeoffs.md @@ -11,3 +11,8 @@ Depending on which model we choose, each one will have their own set of tradeoff **Flexibility** | Ability to adapt to new technologies and introduce new functionalities. | | | **Operational Cost** | Represents the cost of necessary resources to release a product. | | **Reliability** | Reliability captures practices for an application to recover from failure and tools to monitor an application.| | + + +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/008-Best-Practice-for-App-Deployments.md b/pages/03-Cloud-Native/008-Best-Practice-for-App-Deployments.md index 21b64bc..4c65400 100755 --- a/pages/03-Cloud-Native/008-Best-Practice-for-App-Deployments.md +++ b/pages/03-Cloud-Native/008-Best-Practice-for-App-Deployments.md @@ -54,4 +54,9 @@ Helpful for understanding the full journey of a request. ## Resource Consumption Refers to how much resources an application uses to perform its operations. -- usually CPU, memory, network throughput, and number of concurrent requests. \ No newline at end of file +- usually CPU, memory, network throughput, and number of concurrent requests. + + +
+ +[Back to first page](../../README.md##cloud-native) diff --git a/pages/03-Cloud-Native/009-Product-is-Released-Whats-Next.md b/pages/03-Cloud-Native/009-Product-is-Released-Whats-Next.md index 4d4e9d6..440759c 100755 --- a/pages/03-Cloud-Native/009-Product-is-Released-Whats-Next.md +++ b/pages/03-Cloud-Native/009-Product-is-Released-Whats-Next.md @@ -26,3 +26,8 @@ These are some of most common operations you'll encounter after a product goes l - **stale** operation - performed for services that are no longer providing any business value, and should be archived or deprecated. For example, services that were used to perform a one-off migration process. These operations are inevitable and you will perform these as your application grows. At the end of the day, the application exists to provide value to customers and to be easily managed by the technical team. + + +
+ +[Back to first page](../../README.md##cloud-native)