This message was deleted.

How wide do you want to go? Are you looking for "the best toolset" to train yourself? I don't think it really exists. If you want to explore the most facets of platform engineering, my recommendation would be to "Begin at the beginning", use the default hello world application in something like flask or spring and walk your way through a minimum viable platform deployment all the way to "prod." At each step, consider the persona of the most important stakeholder and make decisions on the tools and capabilities they support. For infrastructure and environment paving, you're going to think like an infrastructure engineer and look for good Infra-as-code tools, in CI and code promotion, it's usually the developer and maybe security, in CD it's going to be a blend of personas, as you move farther toward production, you're going to want to think like a platform ops person, and eventually like a chaos engineer and operational security person. If you choose to explore more than a single framework, or take on management of the backing services of a larger platform, you're going to want to look at database tooling, API gateways, authe/o and RBAC, and balancing needs and requirements across your stakeholders and priorities. Oops, now you've got to think like a product manager! 🙂 Throughout the whole effort, you'll be thinking like a finance/business person because I assume you're also working in a homelab/small cloud with an individual's budget. There is no single best toolset, an organization's needs, the existing technologies in use, and the product set to be deployed will determine what tools should be used for which platforms.

I will then create a dummy application and start implementing tools for my practice. I didn't have that much experience, so I will take some time to develop the flow for the application. And I will implement it.

Starting small and building up iteratively really is the essence of running a platform as a product. The most successful platforms I've seen have been built and rebuilt as a learning experience and as stakeholder needs changed.

It’s important to remember Arvind, that learning platform engineering is more than just increasing your knowledge around tech and tools. the largest impact driver of platform engineering comes from the mindset shift to platform as a product and golden paths