This lady has a nice voice and way of talking that is well suited to explaining or teaching things. Some of the other less capable speakers in this conference (and there are many of those) can learn so much from her.
I really enjoyed this short and sweet training video, and I appreciate how she articulate those words easily. Seems easy to grasp her lesson. Anyone know if she has Pluralsight training? Would be very interested here.
Wow this video contained a lot of topics. I think a better title would have been, micoroservices made easy for the experienced user. Thank you trying to show how complex deployments can be managed thru these tools
@@saqwerUA you're right, you can scale the team easier and reduce time to market. But it doesn't mean less complicated, or you can not scale its performance.
Honest question, will full-stack developers (like myself) be required to have deep knowledge of dockers/kubernetes as well of understanding of Cloud+Backend(with architecture and design patterns)+Frontend(React with graphql and Redux)+SQL+Git+CICD (including devops and jenkins)+Testing(yeah, unit tests, integration tests and functional tests)? If true then FML. This seems extremely complicated. Or is this rather a job for DevOps guy or maybe Solution Architect?
Full-stack devs is mostly a myth. There are truly capable engineers that may know VERY DEEP and WELL all of these technologies but it's not the norm and will never be. Full-stack just means you have heard about it and possibly touched some of these tech and will be able to find a working solution for something. It's a jack of all trades and a master of none.
"Jack of all trades, but but master of none, though often better than a master of one" - kindly please finish the quote next time :D imo it depends on the project and problem you are solving. Devs with T-shaped skills i.e deep knowledge of a topic but broad knowledge of many might be the better approach.
After using docker containers (not kubernetes) to deploy to the cloud I am not convinced they are the future. Cloud service providers like Azure are working on developing cloud deployment services that simplify deployment in many ways. I don't see the point in managing deployment in the detail that kubernetes requires. The cloud services should handle that for me. Currently I can believe docker/kubernetes are appropriate for many workloads but probably less so after 5 years or so.
This lady has a nice voice and way of talking that is well suited to explaining or teaching things. Some of the other less capable speakers in this conference (and there are many of those) can learn so much from her.
absolutely!
I really enjoyed this short and sweet training video, and I appreciate how she articulate those words easily. Seems easy to grasp her lesson. Anyone know if she has Pluralsight training? Would be very interested here.
Wow this video contained a lot of topics. I think a better title would have been, micoroservices made easy for the experienced user. Thank you trying to show how complex deployments can be managed thru these tools
It's more complicated than a big monolithic application. To be honest! :)
But at least it's scalable! Lol)
@@saqwerUA you're right, you can scale the team easier and reduce time to market. But it doesn't mean less complicated, or you can not scale its performance.
@@tumivn I'm using node instances but I'll probably have to move to Kubernetes as things grow.
Single NodeJS/Laravel with verticsl scaling would do the trick.
Question: When to choose with microservices architecture?
Helm, Dapr, Service Mesh
Honest question, will full-stack developers (like myself) be required to have deep knowledge of dockers/kubernetes as well of understanding of Cloud+Backend(with architecture and design patterns)+Frontend(React with graphql and Redux)+SQL+Git+CICD (including devops and jenkins)+Testing(yeah, unit tests, integration tests and functional tests)? If true then FML. This seems extremely complicated. Or is this rather a job for DevOps guy or maybe Solution Architect?
Full-stack devs is mostly a myth. There are truly capable engineers that may know VERY DEEP and WELL all of these technologies but it's not the norm and will never be. Full-stack just means you have heard about it and possibly touched some of these tech and will be able to find a working solution for something. It's a jack of all trades and a master of none.
"Jack of all trades, but but master of none, though often better than a master of one" - kindly please finish the quote next time :D imo it depends on the project and problem you are solving. Devs with T-shaped skills i.e deep knowledge of a topic but broad knowledge of many might be the better approach.
After using docker containers (not kubernetes) to deploy to the cloud I am not convinced they are the future. Cloud service providers like Azure are working on developing cloud deployment services that simplify deployment in many ways. I don't see the point in managing deployment in the detail that kubernetes requires. The cloud services should handle that for me. Currently I can believe docker/kubernetes are appropriate for many workloads but probably less so after 5 years or so.
@@metaltyphoon Nope. There are a lot of full-stack developers. You have to be smart and a quick learner but it’s a powerful and lucrative skill set.
Yeah that all is so overwhelming OMG!
Good reference to those tools
Helm, Dapr, Bridge to Kubernates