Let's Go Serverless In The Enterprise!
While reading last week I came across this piece which was interesting to me.
Serverless 101: How to Get Serverless Started in the Enterprise
This line stuck out to me.
"if a company has zero public cloud usage, and zero experimentation internally with new projects such as Kubernetes and Docker, then serverless is not where they should be starting."
That statement is wrong. There's no reason you have to do Kubernetes and Docker first. Your organization is going to have to learn new ideas no matter what. Our opinion at ServerlessOps is if you're just starting your DevOps transformation and/or AWS public cloud transition, do you want to spend most of your time on tools / platform, or people and process? We also see serverless as a way to start slow and iteratively work up to more complex projects. (A container management platform is a complex project to start with.)
However, Ben Kehoe is torn and sees the serverless mindset as a bigger mental leap when coming from an on-prem culture. We accept that fact and realize directly going serverless may not be right for everyone.
So I'm left with a question:
"When does it make sense to leapfrog to serverless and when does it make sense to iterate first towards containers?"
Let me know if you have thoughts!
I'm Tom from ServerlessOps and we provide services to make you successful with your DevOps transformation and enhancement through AWS serverless adoption. Ask us about our training and advisory services.
Also let us know what you think of this week's Cold Start using the 👍/👎 links at the end of this email!
Tom at ServerlessOps