71–80 of 125 posts
One year ago I created this list and demo of databases that are "free forever". I wonder how long it will take until none are left. https://free-databases.vercel.app
Earlier quoted context omitted.
Primary architect of Ubicloud PostgreSQL here. Thanks a lot for shout out! I'd be happy to answer if anyone has any questions about our managed service.
Are you planning on offering a hosted ClickHouse service? After all, for analytical use cases latency doesn't matter so much, hence it would make sense even for companies in other continents to use your service.
I switched to DigitalOcean and it's been a delight. $15/month for a managed Postgres is a good deal, and I am really tired of the hellscape that has become AWS configuration even for the most simplest things. Isn't the whole point of the cloud is simplicity?
The point of cloud was selling businesses on IT as a subscription. And it did start simple as "look ma, no hands managing a database".
But then biggesr cloud providers went and threw themselves heavily at sales to enterprises. And well, they start adding more features for enterprises. And as they add more features, they all more technical and security complex.
Next thing you know, you fired your on premise IT staff and hired just as many if not more staff just to babysit your aws usage. Lol
Or you subscribe to another saas service to try and automate away automating in AWS. Lol
I switched to DigitalOcean and it's been a delight. $15/month for a managed Postgres is a good deal, and I am really tired of the hellscape that has become AWS configuration even for the most simplest things. Isn't the whole point of the cloud is simplicity?
How does one handle a zero downtime migration in this case? On a database of 50gib+ is this a solved problem in Postgres world?
Takes some research but not rocket science.
How does one handle a zero downtime migration in this case? On a database of 50gib+ is this a solved problem in Postgres world?
2. pg_restore to the new database
3. setup replication between the two databases
4. redeploy your service. Usually, deployments are hot swapped so you continue ingesting into your old database, replicating to the new one, until the deployment is complete. If you use sequential identifiers, I don't think it's possible to do this without dropping a few records due to duplication, unfortunately. If duplication is something you cannot handle, you should deploy two instances of your application in parallel, take the original instance down, wait for replication to complete, and then switch to the new one. This will probably be I did something similar recently, but I switched both application hosts and database providers. End user DNS replication would theoretically take some time, but for me consumption dropped to zero within a minute or so https://shottr.cc/s/1ngg/SCR-20240407-hoa.png
This might help people when looking for an alternative. https://wheretohostmy.app/?tech=%5B%22postgresql%22%5D It's a side project I'm currently building so hearing some feedback is highly appreciated.
Also Vultr https://www.vultr.com/products/managed-databases/postgresql/
I switched to DigitalOcean and it's been a delight. $15/month for a managed Postgres is a good deal, and I am really tired of the hellscape that has become AWS configuration even for the most simplest things. Isn't the whole point of the cloud is simplicity?
Hahaha. The point of cloud was selling businesses on IT as a subscription. And it did start simple as "look ma, no hands managing a database". But then biggesr cloud providers went and threw themselves heavily at sales to enterprises. And well, they start adding more features for enterprises. And as they add more features, they all more technical and security complex. Next thing you know, you fired your on premise IT…
