There is this cv-driven-development when you have to use Redis, Kafka, Mongo, Rabbit, Docker, AWS, job schelduers, Microservices, and so on.
The less dependencies my project has the better. If it is not needed why use it?
There is this cv-driven-development when you have to use Redis, Kafka, Mongo, Rabbit, Docker, AWS, job schelduers, Microservices, and so on.
The less dependencies my project has the better. If it is not needed why use it?
After quite a few years of being an employee (and the whole CV driven crap), I’m now in entrepreneur mode, stealth for now (that’s relatively easy, because I’m bootstrapping and funding this with my own money, no investors), and I made an executive decision to (forcibly) think many times, before adopting any “cloudy” thing.
Hardware…is cheap, and bare metal performance outweighs anything cloudy by multiples of magnitudes. If I have to invest money into something, I’d rather invest that in bare metal tooling, than paying for a managed service, that’s just a wrapper around tooling. E.g RDS, EC2, Fargate… or their equivalents across other CSPs.
I can run a Postgres cluster on bare metal, that will obliterate anything cloudy, and cost less than a 3rd if not less. Is it easy? No. But that’s where the investment comes in. A few good Infra resources can do magic, and yes, I hope to be large enough that these labor costs will be way less than a cloud bill.