|
|
|
|
|
by Twaway45609
1979 days ago
|
|
I once closed or deleted our s3 account (was a very long time ago). I recreated or reactivated the account and my files were still there and i got instantly charged all thr fees backwards to the day i closed the account. They reimbursed though the charge. |
|
Haven't this scale of federation of services, "move fast and break things" approach, first to market races and rise of ready to use components and related machinery (containers, k8s, AWS, et al.) abused some well defined norms about technology and as a result aren't we in a somewhat broken state?
In the older days, we'd never have this kind of thing overlooked. You just weren't able to. Now things are much more complicated and this complicated services are assembled in a haphazard way to form big applications and platforms (e.g. too lazy to bind a folder with proper config to enable SSL, so put an NGINX https bridge container in front of it). As a result, the edge cases are not as edge anymore and breaking the configuration of a webapp is much easier.
Similarly this onion structure of abstraction over abstraction makes debugging and mending things much harder. To fix a one-off bug in a DB operation, you need to go to relevant container inside the pod, find its DB location, access if you can and update the table. That table maybe anywhere on this planet. This is impossible for a support engineer in most cases since we have convoluted SSO configurations which makes this kind of access impossible and the original developers couldn't care less in many cases.
I'll sound old, but even the new capabilities are fascinating, we have gone backwards in a lot of things, software quality and robustness related IMHO.