Let me tell you how most, if not all the uneducated cost optimisations start, hit a wall and inevitably never achieve the long term results they’ve set out to realise and how you can avoid some of the pitfalls and save a few thousand, if not millions of $/£/€ along the way.

This post is meant to allow all those companies that are not flooded by VC capital or have budgets to hire 7 figure teams of engineers to look after their cloud estate (a reasonable/unreasonable argument can be made that if you can’t afford said teams, you’re better off going the “buy” route instead of “build” but I digress, that can be a topic for a different post). …

It probably goes without saying that WFH is here to stay, especially if you work in IT like me. The need to be in an office was already limited to “collaboration” and socializing needs but this time in lockdown has caused many of us to reflect on the extensive time we waste in commuting and money we spend in office-related work-habits.

I for one saw my monthly savings dramatically increase since I haven’t been paying £6 per pint or £9 for lunch a few times a week. …

Following-up on the questions I’ve received on Introduction to Terraform Cloud post, today I want to tackle the never-ending debate around repo structures and some of the solutions and their inherent problems. For this conversation, I’ll refer to my IaC in a mostly Terraform oriented way, but most of what follows will apply well to other technologies.

Image for post
Image for post
My attempt at a drawing :)

There are 2 main schools of thought when it comes to infra-as-code repository structures:

  1. Mono Repo: One repository to rule them all, containing all your IaC, your modules and any auxiliary automation
  2. Distributed Repos: “self-contained” repositories that hold the components needed for the solution you’re trying to deliver and referring other repos for reusable components or data…

Before we get started: Sometimes, cloud-based tools and technologies can be quite daunting to adopt for teams. In what I hope to be a series of blog posts, I’ll try to demystify the adoption fears and try to shed some light on a few pitfalls that you might want to avoid when considering tools. If you like this kind of content, find it useful or disagree with me, feel free to let me know by commenting below or tagging me on twitter. 😎

Unless you’ve had your head buried in the clouds for the past few years, you’ve probably come across the term, Infrastructure as Code (IaC). For better or for worse, Terraform is the go-to tool and it’s easy to see why. I’ll keep the reasons why it’s one of my favourite tools to use for another post, but you can see from the data below that it’s seen a meteoric rise in adoption. …


Luis Sousa

DevOps by day, nerd by night — I’m a self-taught cloud platform engineer that loves to tinker with new technologies and build things!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store