Allow disc space to be increased without requiring RAM to be increased
We currently have an 80-ish GB database but we really don't need 8GB of RAM. It would be awesome if we could use a 4GB server and just add more disc space
VPC with Apps, Droplets and Managed Databases
Being able to integrate Apps into a VPC together with droplets and managed databases, would allow secure / private access to them. Maybe even kubernetes could be integrated.
External encrypted backups
The daily cluster backups are great, however they can't protect against accidental cluster deletion (via the UI, or via scripting errors with doctl or terraform). From what I can see once a database cluster is deleted, so are its backups! Having backups decoupled from the cluster or having a mechanism to schedule encrypted exports to spaces would be quite useful.
Use SSL/TLS cert stored in Kubernetes secret
Currently you need to upload the SSL cert manually outside K8s if you want to use it for a load balancer. It would make sense to use the native K8s TLS secret for that. Other providers already support that (e.g. Vultr).
Postgres extension request: pg_roaringbitmap
I would like to request support for pg_roaringbitmap: https://github.com/ChenHuajun/pg_roaringbitmap Roaring bitmaps ( https://roaringbitmap.org ) are state-of-the-art compressed integer bitmaps offering amazing compression and performance. The format is portable, and there are implementations in all popular languages. It's already being used in a number of high-profile open source projects, e.g. Apache Lucene, Apache Hive and Yandex Clickhouse.
Floating IP for Managed Databases
I have tested your managed database service. After a "recovery from a backup" test I found that a second db cluster was created. According to this answer https://www.digitalocean.com/community/questions/floating-ips-for-managed-database an new FQDN is created for the new cluster. In my opinion this is not a good enough design/architecture because it means that I have to change DNS to point to the new FQDN. DNS changes take time to become effective for clients. During this time the clients can't connect to the database even if it is up and running again. To use a floating IP would allow to switch over to the new db cluster much faster. To put it in other words: Why should I pay for a managed HA database service when the design of the solution fails in the worst imaginable scenario (which is a restore from a backup)? Let me know if I have overlooked or misunderstood your solution. If not I hope you can improve on this. Thank you very much.
Allow Postgres Downscaling
Right now, you can pick only instances with SSD size >= from the current one. The issue is that sometimes you need more CPU, sometimes you need more RAM. If you ever happened to use Space optimized droplets there is no way you can scale back for reasonable money. You may need less CPU at one point in time. There are lots of scenarios when you really need it. My proposal is to allow downscaling of instances automatically. Right now you can achieve it by creating a new smaller DB and migrating all data from the old one. I think it can be fairly easily implemented in a managed manner (just create a new, smaller instance, migrate data, destroy old instance) You may put a condition that the new instance must have enough space to accommodate current disc usage +30% for safety reasons.
Transfer app to other User or Team
As people build services for clients, usually they start off with a PoC etc, and use their own company account. But when they want to transfer this away, and to the end client - it is not possible. It would be really nice to be able to transfer an entire App and also an entire Project. Thanks!
URL Rewrites for App Platform Sites
Add a method to create URL rewrites for sites hosted on the DigitalOcean App Platform.