Very good! You nailed it. You are the first one to explain in a crystal clear way that Agility, Elasticity, Micro services, Orchestration (ESB), Keubernetes, Object Storage (where redundancy and eventual consistency are ok) are building blocks of cloud native.
Thank you so much. A good overview. I liked the succint definition - particularly with regard to positioning CN as an architectural and development style. I also liked the comparison between the "old and the new" - similar to what I used to do when positioning RUP :) A good follow on topic would be "Adopting Cloud Native in a Brown Field enviornment i.e. an existing monolithic application." You could include important considerations such as how the application. may have to be refactored. Might be simpler to divide such a migration path in to sections - containerise, orchestrate, refactor, scale / dynamisize. Anyway - a good video for as you can see, you got me thinking :)
Can you correct me, of all the technologies that you described to make a service or application cloud native, non of them requires cloud in order to run these technologies, right ? In other words, they could be implemented without cloud at all, right ?
Nice informative video. One clarification - Isn't what you explained all about making cloud agnostic applications i.e. applications that can be deployed on any cloud provider? I understood cloud native applications to be applications that use the services (or managed services) of one cloud provider (aws/azure/google) to the fullest. That application cannot be shifted to another cloud provider without major code changes. Thoughts?
Very good! You nailed it. You are the first one to explain in a crystal clear way that Agility, Elasticity, Micro services, Orchestration (ESB), Keubernetes, Object Storage (where redundancy and eventual consistency are ok) are building blocks of cloud native.
The best thing is - there is no ambiguity. Everything is very clearly explained without any concept-tangling
The only video I found to clear basics.
Bravo. You explain pretty well.
Glad it was helpful!
Thank you so much. A good overview.
I liked the succint definition - particularly with regard to positioning CN as an architectural and development style.
I also liked the comparison between the "old and the new" - similar to what I used to do when positioning RUP :)
A good follow on topic would be "Adopting Cloud Native in a Brown Field enviornment i.e. an existing monolithic application."
You could include important considerations such as how the application. may have to be refactored.
Might be simpler to divide such a migration path in to sections - containerise, orchestrate, refactor, scale / dynamisize.
Anyway - a good video for as you can see, you got me thinking :)
Thanks for the detailed view David. Appreciate it
Thank you for your clear and well-organized introduction to cloud-native!
Can you correct me, of all the technologies that you described to make a service or application cloud native, non of them requires cloud in order to run these technologies, right ? In other words, they could be implemented without cloud at all, right ?
Any follow up videos on cloud native?
waterfall model??
Can u explain spring cloud contract
Hi Does cloud native app can run offline on client side? Does it run cross platform OS?
Nice informative video. One clarification - Isn't what you explained all about making cloud agnostic applications i.e. applications that can be deployed on any cloud provider? I understood cloud native applications to be applications that use the services (or managed services) of one cloud provider (aws/azure/google) to the fullest. That application cannot be shifted to another cloud provider without major code changes.
Thoughts?
Please can anyone add subtitles to this video? Your video is good but some words are not clear.
Hope you merged micro services and Cloud native together. To go for cloud native, Micro service is not a requirement and vise versa.
Thank you
Good one
2:22 - I hope you're not recording while driving!
Must be a car honking outside the window...if it were traffic it would be massive sound disruption.
lul
Yesa
Too many mid view advertising. Annoying. Distracting. Defeats the purpose of an educational video.
Notes
Watched Thumbed
too much talking and less visuals \ diagrams; this is better suited for podcasts.