5 ms·

Care to elaborate?

• lars_francke 3y ago
  Not OP but even setting up an AWS Account is a roughly hundred step process. Root account, IAM Accounts, I just tried using CLIv2 which asked me to set up something called Identity center first? Billing is complicated, setting up looking and metrics... Another two services. Some other best practice things... Also extra services. AWS is complicated. There is - for me and seemingly others - a lot of value in avoiding this complexity. AWS used to be easy to use for "drive by users". It's not anymore.
  • a2800276 3y ago
    Well put, that's in essence what I meant. If you are using AWS anyway and are accustomed to it, obviously, RDS is a good choice. But I don't want to learn what DNS and Filesystem are called in AWS-speak just to shoehorn myself into getting stuck with AWS forever, when all I need is a hosted database so I don't have to worry about backups, etc. My typical situation sees small to medium (virtual) servers that run software for tens to possibly thousands of users. There are plenty of use cases that aren't "google scale" and can be operated on a simple machine and can profit from a "simple" hosted DB. Rant: Same goes for things like CDNs, I'd guess that 99% of websites don't get nearly the amount of traffic that a simple linux server couldn't handle out of the box. Let alone need sub 100ms ping responses, yet there is this weird cargo cult that requires putting your terraformed, docker stuff running javascript from with a python container with multiple layers of caching behind cloudflare because people don't dare consider simple architectures.