By the way, check out the official CNCF definition (Cloud Native Computing Foundation) definition for clarity.
Cloud-native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.
These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil.
I have been asked about free, online training resources. I have compiled, to my best knowledge, all recent training resources in this post. However, please feel free to add your comments (aka, 2 cents 💰) and extend this list together 🙂
All the training resources could be used by anyone around the glob 24/7. Note that few training resources are geared toward certain US state learning programs.
I truly hope, you could share these resources with your friends, who might be looking for affordable training, and prepare themselves for a better future.
It is usually hard to start a new initiative within a company due to a myriad of reasons. 🤔 Thus, this post will focus on how to follow some descriptive steps in starting a new Cloud Journey whereever you are in your life 🙂
Let’s check a simple approach 💡 below that could guide us on cloud ☁️ (AWS, Azure, GCP, Oracle Cloud) adoption journey 🗺
1️⃣ Step: Check on Team Alignment with cloud fundamentals ✔️ Every team member should have a basic understand of how specific cloud works ✔️ Portfolio of candidate workloads should be available to all team members to be used during strategic, release planning and completion of technical tasks ✔️ The technical strategy should include clarity on which levels of the hosting hierarchy will be used and what those terms mean in our business ✔️ A naming and tagging standard should be established, maintained, and enforced to guide implementation and resource organization ✔️ The hosting hierarchy should be reflected in a resource organization design (account or subscription design) ✔️ Align cloud capabilities, teams, and RACI structure to the fundamental concepts above
As an addition, what would you add into first checklist ? 🤔