Hope you got some valuable information from this video! Please leave a like and share it with your colleagues if it was useful 😊👍

@maxfalc

11 ай бұрын

absolutely!!

@allards

11 ай бұрын

Thanks for making it, it’s giving me energy back to be enthusiast about my career again.

@mdnahidparvez9877

11 ай бұрын

Hi I want to learn Java could you please help me how I learn Java , im new learners

@adewaleadeyinka3146

11 ай бұрын

I did. Thank you so much

@MultiDheerajSharma

11 ай бұрын

great tutorial Nana. Can you share the link to download PPT presented in this tutorial?

Someone sees and searches a lot of videos about the theme... but Nana ALWAYS explains like no one. Thank you!

This video blows me away! I share it with everyone in my organization. I'm an ML Platform engineer. It's exactly as you describe, except we replace "application team" with data science, analytics, ML engineering, and AI research.

i'm 100% certain companies will mess this up and just end up renaming devops to Platform Engineering

@po6577

5 ай бұрын

Yeah this is a great concept but not feasible is most cases. Most company works in chaotic but somehow still delivering products. This add more to the chaotic.

@everwake242

5 ай бұрын

Don't worry, where I work I had this team until 2018 when management decided it was not needed as Devops would fix it. ( today a manager sent me this link as a great idea to promote) circle of....life?

@sdwone

4 ай бұрын

Then maybe we should just stop coming up with new shiny terms and shit, so that we have a chance to catch our breaths and get accustomed to the mess that we all have to deal with NOW then! Seriously... At this rate, Developer Fatigue will soon become a serious problem!!!

@confused6526

Ай бұрын

@@sdwone I do not think this new thing comes form Nana though, to be fair. It is just a new trend of DevOps that in fact, Google has applied to their own work. Be open and see the values and the benefits the Platform team an add to your projects. In fact, contradictory to your last statement. The Platform team will reduce the "Developer Fatigue".

Once again, incredibly done! Thank you very much for clarifying those topics, Nana 👍👍

This topic is really a need of an hour to clarify the confusion between Platform Engineering VS DevOPS . Thanks as always for coming up with comprehensive & clear content Nana. :)

@TechWorldwithNana

11 ай бұрын

Yes, the length was needed to properly explain all the different aspects of it 😊 Thanks for appreciating it!

This was very helpful video. I am in process of setting up Platform Engineering function for my company and taking somewhat off a different approach (combining DevOps, SRE and Platform Architecture) and would love to discuss live with experts like you.

As always , good to see such a relevant topic. Thank you Nana

Power video from powerful lady 😊😊 who is great expert on the DevOps. Nana always comes up with a lot of meaningful videos which will be more helpful. Thank you

@TechWorldwithNana

11 ай бұрын

😊🙏

Love it, great 👍 explanation as always 😊. To see the P in IDP as "Platform" instead of "Portal" was new to me and triggered a few new thoughts, so thanks!

Danke, Nana! Ich bin immer wieder beeindruckt, wie ausgezeichne, suverän und informativ deine Videos sind. Ich arbeite seit rund 1 Jahr genau an diesem Thema und staune einfach wie gut Du das Thema ansprichst und auch sehr verständlich erklärst. Weiter so 🚀

@TechWorldwithNana

11 ай бұрын

Vielen Dank Steve! So ein Feedback zu hören freut mich sehr 😊🙏

As always good to see another brilliant topic. Well articulated with options of influencing others to adopt to this culture. Well done! Thank you Nana

@TechWorldwithNana

11 ай бұрын

Thank you for this great feedback, so happy to hear it's helpful :)

This is so well made! Great work Nana, as a platform engineer I approve!

This clears a lot of clouds in the sky. Thank you much

First video i have got on youtube after seeing many videos related to platform engineering where platform engineering is explained in simple understandable and correct to the point with some extensions of future happenings to it.

@TechWorldwithNana

11 ай бұрын

Thank you Vishal!

Nice video. Nowadays we see more Platform teams and this video is good to know their responsibilities

Wow. This is such an awesome explanation! Thank you so much. Well done! 🙏🏻🙏🏻💓💓

Thanks ... nice and easy grabbing explanation.. It's giving space to think more options instead of strict into single which may vendor lockin...

Wow, another useful one. I didn't even know that there is a role like Platform Engineer, but now I even know what this role's responsibilities are. Great, thanks for the video ❤

@TechWorldwithNana

11 ай бұрын

Thanks for the feedback, happy it was useful for you! :)

My Job got very easy, now I can explain to my friends by showing your video exactly what we do in my organization ( PE + App Devops)

Thanks for your explanation ,I am new to all of this .Learing as I go.👍👍

There is always value to take home listening to you. it was a good use of my time.

As always, Good job and very well detailed video on Platform Engineering. However, I would appreciate if we have a sample IDP platform added to the video. Hopefully we can have that in the next video. Once again, great job Nana!

@TechWorldwithNana

11 ай бұрын

Thanks for the feedback! :)

I'm a DevOps Engineer that works across multiple development teams and I'm already doing what Platform Engineering set-outs - as you should do. Platform Engineers are more of a concern for large organisations that have scaled out of control in isolation of each other (i.e. a DevOps Engineer in every team that might be gathered around a permanent project)

@patelmilind7621

Ай бұрын

Hii sir I'm civil engineering student learning basics of Linux currently and want to make career in devops... .can you please guide me....

@Ycneuqerfesiar

3 күн бұрын

@@patelmilind7621 forward

Perfectly explained as always. Thanks a lot!

WooW amazing pace.. clear flow.. to the point.. well done do e

Thank you for amazing video. Explained so clearly.

To me it often seems more cost and time-efficient to standardize the use of existing cloud PaaS-offerings instead of trying to build something similar in-house. Serverless, ECS, Azure Container Apps etc. If you invest the time to build a great IDP on bare metal you might as-well become a cloud provider yourself.

This video hits me so deep in the soul.

This was very helpful video. Good job and very well detailed video on Platform Engineering.

thanks for this very clear explanation... being an devops engineer; I was wandering what is that team bringing up standards for us and why !! know i know they are platform engineer... making our life easy!! :D

Great elaboration, creastal clearing the roles!

Great explanation. We have a client example if anyone is interested. There were several questions about it here.

So the thing is: you can't eat the cake and have it too. It means that the Platform will take up the huge burden of standardizing various DevOps tech stacks, therefor they will need a lot of different SMEs - in their Platform team - who can properly implement the guardrail, admin and security compliance. But I also see the point of separating Platform team from the traditional DevOps team. This makes a lot fo sense and very practical. If the implementation of Platform team is properly done, then we have a paradise of DevSecOps.... well it is still a big IF as Nana mentioned a few times.

Very well explained 👍

Its really helpful. Can you introduce about Backstage?

@TechWorldwithNana - I’ve already signed up for your DevOps bootcamp program and I’m planning to take CKA certification this year. So, the K8s module from the bootcamp is god enough for the CKA certification or do I need to signup for the CKA course offered by you? Also, I really appreciate your work. I get to learn a lot from your videos. Keep up the good work.

This is what an architecture review board is for. Architects will establish the templates that says what the standards should be so that resources , security and knowledge is reused for all projects.

Brilliant presentation. 💡

This is quality content!

"The content was presented and articulated very well. While I understand that PE can be adopted in large MNCs with multiple teams working on different products, I am curious about how this new role would fit in a startup company with a tech organization of fewer than 200 employees who focus solely on a single product."

you are amazing. great talk as the others.

First of All is like that video without intro! 😉

Inspiring! 💯

Thank you Nana for creating this video and explained with such simplicity Platform Engineering, IDP and how it reduces Cognitive Load for both Dev and Ops and at the same time applying DevOps principles and best practices. While you explained difference between Cloud Engineer Vs Platform Engineer in the video, where does SRE Engineer fit into and what specialized skills required for an SRE Engineer in this model? Should this team be separate or part of Platform Engineering?

@confused6526

Ай бұрын

SRE is for monitoring, performance, and operational of production system. The skill a SRE needs to have is (1) to able to identify where the performance issues are (2) how to improve the performance of the system based on what he/she observes? (3). identify possible cyber attacks in real ti9me., etc...

Wonderful presentation!

Well explained, thanks for that. At 15:00 I was just wondering...wouldn't that be part of SRE role more or less? To define and host the platform, providing a portal to allow DevOps to utilize the environment?

Key success factor for Platform Engineering to be successful is a vision at company level on application architecture. Else App teams will pull the Platform Engineering teams in many directions with too many requirements

Really you are the docker captin., am in india,, but you are the best❤

27:20 I think we should say: application teams, because such a team maybe should not be just developers, they should have an ops person, so they can do proper devops together.

Great introduction 👍

Cognitive overload is an understatement, thanks for describing this.

Thank you for your useful video. One question for the platform which Platform team should offer, need to develop an application or just write the standards and when someone from DevOps team need to use can run the pipeline from Azure or another CI/CD

Well, now I understand who I work for

Could you please let me know, what do you use to create these awesome presentation?

Any video where you covered message ques, Kafka, RabbitQ etc ? Your video's are helping a lot to upgrade myself

You are the best!

Interesting video, thanks Nana!

@TechWorldwithNana

11 ай бұрын

Happy to hear, thank you for your comment! :)

This video should have millions of views!! But I guess the term it is still catching on

Thanks!

one of two devops engineer for a company of 500 people doing cloud/platform and SRE. Good to see a video that outlines it. Lots of people asks what do you do. This video basically sums it all up. Nice.

@confused6526

Ай бұрын

Only two of you? You must be under stress all the time?

Sounds like DevOps with specialized tasks and responsibilities to me. In such setup, a team of devops engineers sitting at higher level with focused on standardization of tools and their configs org-wide. While product-level devops can continue building automation, feedback on the requirements for new tools to them. Thinking about it, who's going to decide on the breaking changes upgrade required for one team which not needed from the rests if they already part of IDP? Most likely that particular team will just have to suck it up and bear with it until the other teams require needs to do so. Or they could be detached from integrated platform and running their own separate instance again which then created a lot of fragmentation forked from the original IDP. This is classic automation and standardization problems across any designation, With the increased requirements, the implementation will be too complicated and hampered away the idea of "standard". I'm just thinking instead of creating a new role of PE, probably devops philosophy should add one more component there is, called collaboration. Probably engineers could be come up with some sort of internal collaboration platform / database that tracks the version, config implementation for their team. Product-level team can refer to this when making changes enhancing collaborative but on much decentralized approach. Much like Git for Platforms and Tools. Then you can have a forum or symposium between multiple devops team every year to collaborate and consolidate some of the tools. That way they dont have to communicate their requirements to another team and stay collaborative and scale as an org-wide team.

Superb explanation! In simple words Platform Engineers does a PhD in one individual tool 🙂.

I work on a company that develops/sells a self service platform. Now that we can use our own product, we are much happier developers 😂

Great video, I do have a question the video focused on development side of things with the application teams and the internal developer platform. How does this work with a transition to Prod? Is it the Platform Team who also manage the deployment into Production?

@zoltannemeth8864

10 ай бұрын

Hi, no, the “Product Team” also called the “DevOps” team in this video not only builds the solution, but they also run it (sometimes with the help of an SRE team).The notion of “handing off” the application to some “ops” team is basically the core of the old IT model. The Platform team tries to automate the infra so that the cognitive load is not so heavy on the Product Team (app team) in terms of having to figure out all the infra stuff. But they (platform team) do not provide “ops” for the app - because if you did that, it would basically just be the old model all over again (slow, inefficient, etc…)

looks like new brand terraform-like approach for devops instruments. But culd anybody bring example of this platform? It looks like a set of rules for big organizations with many teams

I'd be the first buyer of a book that consolidates all the audio script of this video

Hello Nana, first of all thank you a lot for your great videos. I have a question to you. Which IDE would you recommend for DevOps task (as writing jenkins file, ansible tasks, terraform code etc). And it would be very interesting to hear about testing in DevOps. How do you do this (again i'm taking about jenkins file, ansible tasks, terraform code) Thank you

@confused6526

Ай бұрын

Any modern IDEs (VSC, IntelliJ, Eclipse, etc...) will do.

Hi, it would be incredible to have a new premium bootcamp/course updated to use Argo CD and Tekton environment together with aws/azure, kubernetes, ansible, monitoring, etc. Thanks in advance!

@sijjshawn

11 ай бұрын

Argo CD is super easy . Does documentation is not user friendly ? I created & managed many interfaces across many micro services in one Argo CD interface .

Nana never misses.

Funny enough from dedicated teams for dev and ops to DevOps and now it’s changing again to devs, Platform engineers, cloud engineers and Devop engineers

@confused6526

Ай бұрын

DevOps is just a concept. It is NOT a role.

It's weird that I have never seen any platform engineer job description on LinkedIn that mentions this IDP thing!

would the first step by an assessment across the boards on whats tools are being used ?

How "Platform Engineering" would resole following issue: IDP consist o a mongodb cluster (on the cloud) and template to create mongodb databases by the teams. There is a new version of mongodb. Team A wants to use it, but IDP ("Platform") only support previous version of mongodb. Should Platform team update IDP and force everyone to use new version of mongodb or should they create V2 IDP with new mongodb cluster and support 2 clusters (old and new for Team A) ?

Excellent explanation but the more I see the problem, the more I doubt 🤔. Why do people add something in unnecessarily and hope everything will be simplified?🙄 It doesn’t make sense to simplify things by adding something in. Besides, this kind of process may only need by ~1% of the company in the world.😑 Shouldn’t they limit the tech stacks and standardize them by policies then focus on the business competition?🤔 Shouldn’t they use their current tech stacks proficiently effectively efficiently instead of knowing it shallowly from tutorial?🤔 Problem -> Add something in -> Find more people to do -> Human resource cost -> Problem 😂😂😂

do you have a Devops bootcamp focused around GCP instead of AWS?

This platform team are only required on large company that develops tens so on software with tons microservices. One DevOps team to standardizing pipeline, so every programmer only working on top of those. It's scalable in pursue of smaller user member workers. But why not build own cloud on top of own bare metal? I think it's better rather than paying rent cost for cloud. That's supposed to be platform team and DevOps team works closely.

Thanks

@TechWorldwithNana

11 ай бұрын

Thank you Neil!

@nimam3530

11 ай бұрын

@@TechWorldwithNana thank you for providing such excellent and well-polished content.

hello, mind me asking which software do you use for the animations?

How do I start with deploying an Internal Developer Platform? Are there already existing technologies for that?

@confused6526

Ай бұрын

There's no such thing as Platform Technologies. It is a task that one can implement using existingZIaC tech stacks. Start small as NanA describes in the video and ramp it up gradually when your Platform gets more mature over time.

How do you fill in gaps that are missing on the platform? Like if the platform team has not defined some terraform modules that an application team needs. Does Application team wait for the module to be developed? Does the application team write the terraform module?

@confused6526

Ай бұрын

That is not what Platform team should do. What it should do is to come up a standardized, generic, general templates where the App team can simply use them by injecting them with their own parameters. Pleas re-watch the video again when Nana talked about "Parameters" thing.

This is another layer of Cloud Operations

Meta is on a whole different standard when it comes to profiling and past profilung but we live in the present so what does that matter to us as it is memories.Virtualization.

Any examples of IDPs that already exist so the platform team doesn't have to develop it from scratch?

Which tool have you used to create this video?

Wow

Standarization and Tools, technology consistency is Enterprise Architecture Team Role and who is a bridge between teams

@confused6526

Ай бұрын

hummm ...I think you need a "Solutions" Architecture Team. Not an "Enterprise".

Anyone remembering the time when for deployment it was sufficient to upload a file? I think, nowadays some things in IT go totally wrong. Do we really need all that stuff? I only have very basic knowledge of Kubernetes, but if you need two separate certifications for administration and deployment for frameworks like this, then something goes terribly wrong and we must ask, if at this point this is not generating more problems and work than it helps avoiding.

I think giant companies will make a product for all tools and then sell it to other small companies. Is this possible?

@confused6526

Ай бұрын

it is possible and doable. It need a lot funding and efforts to build such a one-size-fit-all product.

What's up Nana❤❤❤

most underrated topics which you have explained in the best way, really helpful, thanks @TechWorldwithNana :)

@TechWorldwithNana

11 ай бұрын

Thank you Muhammad, appreciate your comment :)

But self service development is an additional tool that the company needs to support + there is no way to implement project specific optimisations on the platform.

When you say Devops teams do you mean cross functional teams

summary: platform just combines devOps, Cloud and security all into one

@AxaGarcia

3 ай бұрын

Haha yeah right

@confused6526

Ай бұрын

And that is called "DevSecOps".

only downside I can mention in your videos is it is lean to open source products and trying to not mentioning main tools like in cicd area, less than 15% of market working with gitlab(it is open core not open source), but we continue hearing it's name in your videos, not the top tools.

(only at about 9.5minutes in so far) Up to now it sounds like the "Ops" in Devops has become too complex as BOTH Dev and Ops got more and more complex over time so that we.. extract the Ops out again and call it Platform Engineer? 🤣😅

For me all this farse called devops was an excuse to reduce people and force Devs to know ops stuff, and Ops knows devs stuff. Now they see that is impossible to have unicorns all over the company and those ones so called unicrons are not going to work for peanuts. So new roles will appear to be the traditional way but with less limitations. Now the next step will be try to find unicorns outsourcing to countries like India where they will work for peanuts and 60 to 70h per week with the promise to get an H1B visa that maybe would not arrive.

Looks like a DevOps guy now needs to have additional skills of U.I(Java Script) & DBMS knowledge , apart from Multi-Cloud DevSecOps skills ? Great.

@user-yq8qw9yg6e

6 ай бұрын

basically greedy shareholders and CEOs who earn millions decided to reduce the amount of slaves and put them more work for less money so they can have a hole IT department on a 1 person. And if they can ,they will outsorce that person to pay even less. This will end badly

I love u nana

19:16 yeah yeah, I already image how app team waits for year while platform team hiring an expert and configuring their platform. And literaly might takes years. This is a same as it was before DevOps.

@allards

11 ай бұрын

In some sense, it’s a logical step back to separate off platform operations from the application development. I see a big difference; this time the application developer team is responsible for running the Apps they built, but they don’t have to figure out the platform while they're juggling other Dev / Deployment responsibilities. Before, Ops (PE) had to run Apps they had no knowledge about, now Dev is empowered to run those themselves and Ops people can do what they are good at, maintaining reliable application / dev platforms. All this keeping the DevOps mindset of course.