|
1 | | -# Cloud-Native |
2 | | - |
3 | | -## Introduction |
4 | | - |
5 | | -Cloud is everywhere. Today, many companies want to migrate their |
6 | | -applications on to cloud. For this migration to be done, the |
7 | | -applications must be re-architected in a way that they fully utilize the |
8 | | -advantages of the cloud. |
9 | | - |
10 | | -<iframe width="560" height="315" src="https://www.youtube.com/embed/fp9_ubiKqFU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
11 | | - |
12 | | -## Presentations |
13 | | - |
14 | | -[Cloud-Native Presentation :fontawesome-regular-file-pdf:](./materials/01-What-Is-Cloud-Native.pdf){ .md-button target=_blank} |
15 | | - |
16 | | -## What is Cloud-Native? |
17 | | - |
18 | | - |
19 | | -Cloud-native is about how we build and run applications taking full |
20 | | -advantage of cloud computing rather than worrying about where we deploy |
21 | | -it. |
22 | | - |
23 | | -Cloud-native refers less to where an application resides and more to how |
24 | | -it is built and deployed. |
25 | | - |
26 | | -- A cloud-native application consists of discrete, reusable components |
27 | | - known as microservices that are designed to integrate into any cloud |
28 | | - environment. |
29 | | - |
30 | | -- These microservices act as building blocks and are often packaged in |
31 | | - containers. |
32 | | - |
33 | | -- Microservices work together as a whole to comprise an application, |
34 | | - yet each can be independently scaled, continuously improved, and |
35 | | - quickly iterated through automation and orchestration processes. |
36 | | - |
37 | | -- The flexibility of each microservice adds to the agility and |
38 | | - continuous improvement of cloud-native applications. |
39 | | - |
40 | | -**CNCF Cloud Native Definition** |
41 | | - |
42 | | -Cloud native technologies empower organizations to build and run |
43 | | -scalable applications in modern, dynamic environments such as public, |
44 | | -private, and hybrid clouds. Containers, service meshes, microservices, |
45 | | -immutable infrastructure, and declarative APIs exemplify this approach. |
46 | | - |
47 | | -These techniques enable loosely coupled systems that are resilient, |
48 | | -manageable, and observable. Combined with robust automation, they allow |
49 | | -engineers to make high-impact changes frequently and predictably with |
50 | | -minimal toil. |
51 | | - |
52 | | -The Cloud Native Computing Foundation seeks to drive adoption of this |
53 | | -paradigm by fostering and sustaining an ecosystem of open source, |
54 | | -vendor-neutral projects. We democratize state-of-the-art patterns to |
55 | | -make these innovations accessible for everyone. |
56 | | - |
57 | | -## Why Cloud-Native? |
58 | | - |
59 | | -Cloud-native applications are different from the traditional |
60 | | -applications that run in your data centres. The applications that are |
61 | | -designed in the traditional way are not built keeping cloud |
62 | | -compatibility in mind. They may have strong ties with the internal |
63 | | -systems. Also, they cannot take advantage of all the benefits of the |
64 | | -cloud. |
65 | | - |
66 | | -So, we need a new architecture for our applications to utilize the |
67 | | -benefits of cloud. There is a need to design the applications keeping |
68 | | -cloud in mind and take advantage of several cloud services like storage, |
69 | | -queuing, caching etc. |
70 | | - |
71 | | -- Speed, safety, and scalability comes with cloud-native applications. |
72 | | - |
73 | | -- Helps you to quickly deliver the advancements. |
74 | | - |
75 | | -- Allows you to have loose ties into the corporate IT where it most |
76 | | - certainly would destabilize legacy architectures. |
77 | | - |
78 | | -- Helps you to continuously deliver your applications with zero |
79 | | - downtime. |
80 | | - |
81 | | -- Infrastructure is less predictable. |
82 | | - |
83 | | -- Service instances are all disposable. |
84 | | - |
85 | | -- Deployments are immutable. |
86 | | - |
87 | | -- To meet the expectations of the today’s world customers, these |
88 | | - systems are architected for elastic scalability. |
| 1 | +# Cloud Concepts |
89 | 2 |
|
90 | 3 | ## Cloud-native concepts |
91 | 4 |
|
@@ -289,6 +202,10 @@ practice, you can conduct experimentation. Based on the feedback from |
289 | 202 | business, you can quickly and safely deliver your applications that can |
290 | 203 | scale. |
291 | 204 |
|
| 205 | +## Presentations |
| 206 | + |
| 207 | +[Cloud-Native Presentation :fontawesome-regular-file-pdf:](./materials/01-What-Is-Cloud-Native.pdf){ .md-button target=_blank} |
| 208 | + |
292 | 209 | ## Cloud-native Roadmap |
293 | 210 |
|
294 | 211 | You can define your cloud native road map in many ways. You can get |
@@ -366,8 +283,6 @@ to check this out. |
366 | 283 |
|
367 | 284 | ## References |
368 | 285 |
|
369 | | -- [Learn Cloud-native](https://www.ibm.com/cloud/learn/cloud-native) |
370 | | - |
371 | 286 | - [John Gilbert, (2018). Cloud Native Development Patterns and Best |
372 | 287 | Practices. Publisher: Packt |
373 | 288 | Publishing](https://learning.oreilly.com/library/view/cloud-native-development/9781788473927/) |
|
0 commit comments