4 ms·
There more benefit than that. One example...development teams can't force the same level of tech debt that they can on-prem. If Amazon's upgrading some servic
by tyingq 7y ago
There more benefit than that. One example...development teams can't force the same level of tech debt that they can on-prem. If Amazon's upgrading some service or competent, there isn't any bargaining or exceptions.
Many similar benefits when you have a huge for-profit entity running the infrastructure at their scale. They optimize a lot for you.
- pvorb 7y agoBut you usually also have to wait longer for new versions of services -- which might not be a problem for the majority, but can be a show-stopper for some.
- dragonwriter 7y ago> If Amazon's upgrading some service or competent AWS almost never forcibly spins down legacy functionality, even if they stop advertising it, unless literally no one is left using it. That's actually a selling point of AWS to enterprise: while idealistic devs may like “our cloud vendor will force us to use the latest and greatest so we don't have to have that fight”, enterprise buyers don't want “we’re going to be compelled to reengineer our working systems on someone else's timetable”.
- tyingq 7y agoRDS might be one example. No forced upgrades from AWS on it? Or AMIs? K8S versions in EKS? Etc.
- dragonwriter 7y agoRDS has user-controlled optional automatic patching and (for SQL Server at least) minor version upgrades. It doesn't have forced upgrades, AFAIK.