In the past 15 years of my professional work life as System Architect, I have seen and worked on it all: Pet servers, carefully managed by senior sysadmins, cheap shared hosting, enterprise scale, redundant server rooms with racks full of bare metal and cloud services from DigitalOcean to Azure and AWS. All those hosted precious, boring and often obsolete or completely forgotten stacks and appliances. The model of provisioning software and configuration on these boxes differed highly. Some were cared about by dedicated sysadmins, others were provisioned using tools like Ansible or Puppet.
Now, that I started my own (secret) project, I revisited and thought through a lot of these concepts. Therefore I have settled with AWS as hosting environment and Terraform as configuration and setup tool. The reasoning for not jumping on the band wagon with host-as-you-go solutions like Amplify, Zeit Now and friends is that I wanted to the foundation right and learn something along the way. I have just too often seen cowboy code that goes in production. And cowboy code that stays in production and later on justifies whole departments taking care about it.
Workaround as a workflow.
…is what I call these kinds of setups, when I consult IT. If you find yourself struggling with well executed and maybe over engineered setups, you can follow @gtmifylabs on Twitter. This is the account for my project, where I share my findings, my struggles and my fails in public. Got advice? Comment! Are you interested? Follow!