Re: updating what it means to be "Cloud Native"
Justin Garrison <justinleegarrison@...>
toggle quoted messageShow quoted text
I'm glad so many people found my definitions helpful!
I disagree that applications have "always been designed for resiliency, operability, and observability". I have worked on numerous systems that had none of those qualities.
While I obviously agree that agility is important and a key differentiating factor in a cloud environment in this condensed definition I was lumping agility into "dynamic". See my expanded definition from my previous email.
I'm sure there are opinions about things being agile, dynamic, and high velocity but at the end of the day I think it's all about the ability to change frequently to provide business value. No matter if that's the applications or infrastructure or if change is allowing a pivot (agility) or faster time to market (velocity). The DevOps movement really started this as a thing to aspire to with how many deployments per day you had. Sadly I think that was the wrong metric to measure but nonetheless defined much of that culture. Cloud native can empower lots of deployments per day (building on DevOps principles) but we should try to measure impact to the business instead of how fast we go.
On Wed, Jan 31, 2018 at 10:00 AM, Scott Hammond <scott.hammond@...> wrote: