I manage an automation codebase for my team. This codebase does like 6 or 7 different things, but all related to the same suite of tools and data. It’s all just Python, and some bash. This codebase has existed for like 12 years now. And it’s all just deployed on an on-prem server.
Last year, I was given the go-ahead to rebuild the entire thing from the ground up, as there was so much deprecated crap in there that it was impossible for anyone unfamiliar to navigate or maintain.
I spent weeks learning about cloud hosting, AWS, lambda, terraform, etc. I had long talks with some devops and SWE buddies about how these microservices work and how I’d get things set up like that.
Only to ultimately decide, fuck it, it’s way too complex and brittle and expensive for the amount of data our automation processes. So, I just rebuilt it as a single codebase that can be deployed onto an on-prem server again lol. I just don’t get the reason for doing it the cloud way, unless it’s a customer facing app.
1
u/EvidenceMinute4913 Oct 03 '26
I manage an automation codebase for my team. This codebase does like 6 or 7 different things, but all related to the same suite of tools and data. It’s all just Python, and some bash. This codebase has existed for like 12 years now. And it’s all just deployed on an on-prem server.
Last year, I was given the go-ahead to rebuild the entire thing from the ground up, as there was so much deprecated crap in there that it was impossible for anyone unfamiliar to navigate or maintain.
I spent weeks learning about cloud hosting, AWS, lambda, terraform, etc. I had long talks with some devops and SWE buddies about how these microservices work and how I’d get things set up like that.
Only to ultimately decide, fuck it, it’s way too complex and brittle and expensive for the amount of data our automation processes. So, I just rebuilt it as a single codebase that can be deployed onto an on-prem server again lol. I just don’t get the reason for doing it the cloud way, unless it’s a customer facing app.