3 ms·
The risk of a one-man operation in this case is pretty clear. If the one dude running this gets hit by a bus, your dev environment vanishes and is useless, all
by TheDong 5y ago
The risk of a one-man operation in this case is pretty clear.
If the one dude running this gets hit by a bus, your dev environment vanishes and is useless, all data lost.
If you instead use LightSail, it's clearly better. You'd need quite a few Amazon employees to be on the same bus before a small accident would result in LightSail vanishing and becoming useless.
With both this, and hand-rolled stuff on LightSail, if you get hit by a bus yourself, of course the environment is useless, but that's an identical risk for both of them.
- blunte 5y agoThese days, aside from configuration (which is no small thing), one's data is often stored or at least very frequently backed up in the cloud. If this service vanished overnight, you would likely just lose the time it takes to tune a similar dev environment. If you have a git repo with your dot files and such, and you use symlinks where possible in your tools to refer to your master config repo, then re-setting up your dev env can be nearly instant. If this service was database hosting, then I would be more concerned about 1-person operation.
- movedx 5y agoFair. But would you rather know it's a one man operation and avoid it, or not know, thinking there is a team, and then get stung in the manner you're suggesting?
- PeterStuer 5y agoIn many midsize and large enterprises critical functions are not redundant. There is just the one person knowing how to do X or Y. If that one person disappears, your service will be down for a long time even if the company still exists.