Cover Image Credit: Thanks James Bowman!

I've spent a lot of time recently writing about Cloud Engineering. The more I learn about Cloud, the more I'm humbled (and quite frankly, scared) about how much there is to know...

Wanna learn Serverless? Sure, you need an AWS account, oh and it needs to be setup securely, oh and your Lambda needs an IAM policy. Oh and you'll also need to know a programming language too, right? Oh! And you'll need to understand events... and logging, you'll want some of that too... What's the difference between logs and metrics? Who knows! Just remember to structure those logs! (What the hells a structured log?). Oh and you wanna make sure your error handling is setup right, too. Oh and don't forget to access your Lambda you'll need to hook up to API Gateway (maybe you should use Serverless framework?). You'll probably wanna learn infrastructure as code, too otherwise things will get messy. Oh and since we're building an API we better make that RESTful compliant, too. And we'll want an API standard, how about JSON:API? Or GraphQL? How should we test that? Integration testing? On Local?

You get the point (ha! And I really, really could keep that example going on!). All that for potentially just a single API...

So my question is: What Cloud technologies are you trying to learn at the moment, and what are some of the hurdles you're facing? What techniques and concepts are you looking into, and what things are you ignoring?

Lou is the editor of The Cloud Native Software Engineering Newsletter a Newsletter dedicated to making Cloud Software Engineering more accessible and easy to understand, every 2 weeks you’ll get a digest of the best content for Cloud Native Software Engineers right in your inbox.