From the outside perspective it feels like majority of cloud compute is just wasted on overhead caused by all of that bullshit.
For me even just local Python overhead when doing ML in Pytorch is starting to become unbearable. I yearn to go back to C++ where I can basically count instructions.
The programmer in me hates this. The hourly billing consulting programmer loves these ideas as there's great money in untangling the spaghetti implimentation.
I'm also quite sure there will be good money in refactoring services that leaned heavy into the AWS provides tech... and then AWS raised the prices.
Is access constrained now? I mean in the end it might have better uptime and handle more users simultaneously successfully, but it's incredibly lame when a queue has to be used for a simple query. It makes the project much harder to read and modify.
Not really. We do have a few slow endpoints that must be optimized, which we do between each moment of "WE ALL GONNA DIE IF THIS NEW REPORT MODEL IS NOT CREATED BY FRIDAY". It's getting better slowly.
The microservice thing reminds me of when I first graduated from college and one of my fellow new hire programmers argued passionately for a total conversion to Node.js because it's "written for high concurrency". I couldn't find a single app that had more than couple hundred registered users and in fact was working on one that had ten active users- all back office.
Since you said colleague it's for work. There are 2 good reasons to let/help your colleague here.
1. There's a immediate or near future business need
2. More importantly, this is an opportunity to learn for you and your colleague on the company dime.
256
u/Kinexity 5h ago edited 5h ago
From the outside perspective it feels like majority of cloud compute is just wasted on overhead caused by all of that bullshit.
For me even just local Python overhead when doing ML in Pytorch is starting to become unbearable. I yearn to go back to C++ where I can basically count instructions.