|
|
|
|
|
by sksjvsla
357 days ago
|
|
It is more trivial than it seems. How did people manage a Postgres instance prior to RDS? Of the entire feature list, what parts of RDS do you use? 1. Dumping a backup every so often? 2. Exporting its performance via Prometheus, and displaying in a dashboard? 3. Machine disk usage via Prometheus? 4. An Ansible playbook for recovery? Maybe kicking that into effect with an alert triggered from bullet 2 and 3. 5. Restoring the database that you backed up into your staging env, so you get a recurring, frequent check of its integrity. This would be around 100 to 500 lines of code of which an LLM can do for you. What am I missing? |
|
Besides this we also use - ECS to autoscale app layer - S3 + Athena to store and query logs - Systems Manager to avoid managing SSH keys. - IAM and SSO to control access to the cloud - IoT to control our fleet of devices
I’ve never seen how people operate complex infrastructures outside of a cloud. I imagine that using VPS I would have a dedicated dev. ops acting as a gatekeeper to the infrastructure or I’ll get a poorly integrated and insecure mess. With cloud I have teams rapidly iterating on the infrastructure without waiting on any approvals and reviews. Real life scenario 1. Let use DMS + PG with sectioned tables + Athena 2. Few months later: let just use Aurora read replicas 3. Few months later: Let use DMS + RedShift 4. Few months later: Zero-ETL + RedShift.
I imagine a dev. ops would be quite annoyed by such back and forth. Plus he is busy keeping all the software up to date.