Skip to content

Commit 112e3ea

Browse files
authored
Merge pull request #11 from ibm-cloud-architecture/bak-updateCloudNative
Bak update cloud native
2 parents a9d5c09 + b844337 commit 112e3ea

30 files changed

+106
-262
lines changed

docs/agenda.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ The following table lists the topics and coding activities for the week. Click o
1010
| --------------------------------------------------------------------- | --------------------------- |
1111
| Kickoff | Activity |
1212
| Introductions | Activity |
13-
| [Introduction Cloud Native](cloud-native/index.md) | Presentation |
13+
| [Introduction Cloud Native](cloud/index.md) | Presentation |
1414
| [Containers](./containers/index.md) | Presentation |
1515
| [Container Activities](./labs/index.md#containers) | Activity |
1616
| Lunch | Activity |

docs/cloud-native/app-dev.md

Lines changed: 0 additions & 156 deletions
This file was deleted.

docs/cloud/benefits.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
# Benefits of Cloud

docs/cloud/cn-apps.md

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
# Cloud Native Applications
2+
3+
## What is Cloud-Native?
4+
5+
Cloud-native is about how we build and run applications taking full
6+
advantage of cloud computing rather than worrying about where we deploy
7+
it.
8+
9+
Cloud-native refers less to where an application resides and more to how
10+
it is built and deployed.
11+
12+
- A cloud-native application consists of discrete, reusable components
13+
known as microservices that are designed to integrate into any cloud
14+
environment.
15+
16+
- These microservices act as building blocks and are often packaged in
17+
containers.
18+
19+
- Microservices work together as a whole to comprise an application,
20+
yet each can be independently scaled, continuously improved, and
21+
quickly iterated through automation and orchestration processes.
22+
23+
- The flexibility of each microservice adds to the agility and
24+
continuous improvement of cloud-native applications.
25+
26+
<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>
27+
28+
## Why Cloud-Native?
29+
30+
Cloud-native applications are different from the traditional
31+
applications that run in your data centres. The applications that are
32+
designed in the traditional way are not built keeping cloud
33+
compatibility in mind. They may have strong ties with the internal
34+
systems. Also, they cannot take advantage of all the benefits of the
35+
cloud.
36+
37+
So, we need a new architecture for our applications to utilize the
38+
benefits of cloud. There is a need to design the applications keeping
39+
cloud in mind and take advantage of several cloud services like storage,
40+
queuing, caching etc.
41+
42+
- Speed, safety, and scalability comes with cloud-native applications.
43+
44+
- Helps you to quickly deliver the advancements.
45+
46+
- Allows you to have loose ties into the corporate IT where it most
47+
certainly would destabilize legacy architectures.
48+
49+
- Helps you to continuously deliver your applications with zero
50+
downtime.
51+
52+
- Infrastructure is less predictable.
53+
54+
- Service instances are all disposable.
55+
56+
- Deployments are immutable.
57+
58+
- To meet the expectations of the today’s world customers, these
59+
systems are architected for elastic scalability.

docs/cloud-native/index.md renamed to docs/cloud/cn-concepts.md

Lines changed: 5 additions & 90 deletions
Original file line numberDiff line numberDiff line change
@@ -1,91 +1,4 @@
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
892

903
## Cloud-native concepts
914

@@ -289,6 +202,10 @@ practice, you can conduct experimentation. Based on the feedback from
289202
business, you can quickly and safely deliver your applications that can
290203
scale.
291204

205+
## Presentations
206+
207+
[Cloud-Native Presentation :fontawesome-regular-file-pdf:](./materials/01-What-Is-Cloud-Native.pdf){ .md-button target=_blank}
208+
292209
## Cloud-native Roadmap
293210

294211
You can define your cloud native road map in many ways. You can get
@@ -366,8 +283,6 @@ to check this out.
366283

367284
## References
368285

369-
- [Learn Cloud-native](https://www.ibm.com/cloud/learn/cloud-native)
370-
371286
- [John Gilbert, (2018). Cloud Native Development Patterns and Best
372287
Practices. Publisher: Packt
373288
Publishing](https://learning.oreilly.com/library/view/cloud-native-development/9781788473927/)

docs/cloud/index.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Journey to the Cloud
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+

0 commit comments

Comments
 (0)