3 ms·
The common thread seems to be unexpected massive bills from running jobs on third party servers.
by hermitcrab 3y ago
The common thread seems to be unexpected massive bills from running jobs on third party servers.
- thelastparadise 3y agoYeah I think I'd rather deal with a server or two of my own getting overloaded than having some kind of huge unexpected bill.
- expertentipp 3y agoBut everyone wants to work on geodiversified autoscaling superclusters. It starts with watching a presentation on AWS or Azure on YouTube, or even innocent Medium article.
- hermitcrab 3y agoIndeed. But a half way decent PC running halfway efficient software can generally easily process datasets with millions of rows. It is only when you get into billions of rows that you really need to start worrying about scaling.
- uoaei 3y agoRealistically, it starts as a byproduct of the turn toward Resume-Driven Development (RDD).
- marginalia_nu 3y agoThe bills aren't the only externalities from this design decision. Worked in an office a few years ago, brand new state of the art everything. Even the light switches were so damn modern and 201Xs that the lights were controlled by a server somewhere. Funny thing happened when you pressed both the on and off button at the same time[1], based on empirical observatgions, both the turn-on-lamp and turn-off-lamp processes would spawn, and they'd both race against each other, almost turning the light on, almost turning the light off. So we got flickering disco lighting until someone called a technician to reboot the server. Good times. [1] of course on and off they were discrete buttons, rocker swiches are so outdated.