There are many different books on the topic of Cloud Software Engineering, but no one book could possibly cover everything. So dependent on what you’re looking for I’ve made some suggestions here of the books which have made the biggest impact on me, broken by category. Everything from getting to grips with microservice architecture to understanding DevOps culture.
All the books on this page are books I have copies of. I don’t recommend anything that I wouldn’t buy, or haven’t read. I personally buy most books as hardcopies as I like to make notes in them, but you do whatever works for you.
TL;DR; What I Recommend
If you’re short of time, here’s the books I’d recommend:
- Hearing a lot about the “DevOps“? But don’t know where to start understanding what it is? Check out: DevOps Handbook (click to check the current price on Amazon)
- Have most of the basics of backend engineering down? Want to get better at understanding cloud architecture patterns? Check out: Building Microservices (click to check the current price on Amazon)
- Got decent software engineering skills, but looking to brush up on your cloud infrastructure? Check out: Terraform up & Running (click to check the current price on Amazon)
- Thinking to take an AWS exam? Or brush up on the main AWS services? Check out: AWS Certified Solutions Architect Study Guide (click to check the current price on Amazon).
- Applying for a job? And trying to figure out how best to lay out your CV (resume) and what to focus on? Check out: The Tech Resume: Inside Out.
Okay, but if you’re after a bit more of a break down of each book, why I like it and why I’d recommend it, read on!
For Cloud Architecture: “Building Microservices: Designing Fine-Grained Systems”
There are many different aspects to cloud architecture, and microservice architecture isn’t the only way to build in the cloud. However, I can be pretty sure that if you’re working in the cloud you’re going to come into contact with microservice architecture somewhere.
Building Microservices (click to check the current price on Amazon) is a great introduction to the basic principles of the architectural patterns of microservices, what to look out for and what to avoid. I really like how Sam doesn’t hold back on sharing his personal opinions and thoughts throughout the book.
For “DevOps” Culture: “The DevOps Handbook”
Work in cloud / software engineering for two minutes and you’re going to hear the term “DevOps”. Whilst I actively try to avoid. But the DevOps Handbook (click to check the current price on Amazon) was the book that I found the most approachable. It’s quite textbook-y so you might want to dip in and out of it as you see fit, but it’s a great introduction to lots of practices, from CI/CD to blue/green deployments. If you’re not so strong on these areas, I recommend checking it out.
For Infrastructure As Code: “Terraform Up & Running”
There are quite a few books out there about Infrastructure As Code generically speaking. But, I’d rather just go straight to recommending a specific technology, Terraform. Why? Terraform is agnostic of cloud vendors, so it works in GCP, Azure, etc, it’s declarative (which is exactly what you want from an Infrastructure As Code tool) and it has a growing community.
And if you want to learn Terraform, one of the best resources is Terraform up & Running (click to check the current price on Amazon). It’s written by Yevgeniy Brikman who I know has spent a lot of time in the trenches using Terraform in many different formats and situations so you know the advice is solid.
For An AWS Reference: AWS Certified Solutions Architect Study Guide
If, like me, you find staring at a computer screen 24/7 often overwhelming you might be open to the idea of reading about what you’re learning rather than watching, etc. If that’s the case, and you’re learning AWS, or are trying to get certified you can check out the AWS Certified Solutions Architect Study Guide (click to check the current price on Amazon). I do think your best shot for learning is hands-on, however if you need a break and you want to brush up on some services, the book can be a useful companion.
For Applying To Jobs: The Tech Resume Inside Out
The Tech Resume: Inside Out is one of those books that most software engineers might have considered writing themselves due to how many times we get asked about tips for applying to jobs, and CV writing, etc. In the Tech Resume: Inside Out book Gergely dives into every different aspect of the software developer CV that you’d want to know.
I learned quite a few neat tricks in the book, that I didn’t consider before. The books very well researched, and has inputs and insights from various different industry experts and leaders, it’s not just a book full of one dudes opinions.
Seriously, I recommend it a lot. If you’re trying to get a job and you’re applying and maybe getting no luck, I’d highly recommend it. Or, even if you’re like me, a more seasoned software developer I can guarantee that you’ll learn something new, or it’ll change your perspective on how you write your CV.
And if you still want to know more, you can also read a Tweet thread I posted of my thoughts on the book, too:
I recently found the time to read a (graciously gifted) copy of @GergelyOrosz “The Tech Resume: Inside Out”.
I had some of my own hunches validated, and some questions answered.
Here’s 3 things that stood out to me about the book, and some things I took away from it…
— Lou 👨💻🏋️♂️🎸🚴🏻♂️🏍 (@loujaybee) January 2, 2021