Today's thread is about an @awscloud case study: @monzo. It can be found at aws.amazon.com/solutions/case…
Monzo has half a million customers, was founded in 2015, and *is a freaking bank*. As in "regulated." As in "the UK government will stomp them back to the stone age if they screw things up."
Look at the services they use: EBS, EC2, S3, CloudTrail, Organizations, and AutoScaling. Sounds like a legacy environment that's boring right? Wrong! These are trusted, stable services.
Remember that the Venn diagram of "what really powers companies" and "what gets a lot of attention on stage" isn't a circle.
I can say that a majority of the spend I see on AWS (comfortably north of $1 billion a year) is on EC2. Add in RDS, S3, data transfer, and EBS, and what's left over generally distills down to "that's cute."
Whatever you build has to work for your constraints. I don't know what they are; you presumably do. Maybe for you, Serverless is a pipe dream.
Maybe multi-cloud is a business requirement.
Maybe Kubernetes will add tremendous value to--hahahah I'm sorry, I can't suspend that much disbelief. The others are good though.
My point is that if you look at videos from reInvent last week, you'll see a lot of shiny things. Don't feel bad. Not everything is for you, and that's okay.
Just because it's trendy doesn't mean it's the right answer. Conversely just because it's not ten years old doesn't mean it doesn't have value. Do what's right for your environment. Gartner has no answers for your constraints.
