Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Digital Ocean Managed Databases

try.digitalocean.com

Post reply on HN
Print view View original

51–60 of 171 posts

Re: Digital Ocean Managed Databases

#51

Post by Ataraxy »

tyingq wrote: post #39

So now they have managed databases, load balancers, a cloud firewall that's partially VPC like, object storage and block storage. Assuming managed K8S is next, or maybe more "AZ/Region" h/a features. Great to have a new player coming into this space. Especially one with reasonable egress charges.

One thing I imagine that's coming at some point is their own implementation of "cloud functions".

Re: Digital Ocean Managed Databases

#52

Post by manigandham »

doh wrote: post #27
brightball wrote: post #23

Sweet mother! #1 thing you can do to make this compete with RDS and Cloud SQL would be to support extensions out there that they don’t. HypoPG needed by Dexter, pg_partman, etc. Lack of certain extensions is the biggest failing of those offerings IMO.

I believe most of those are offered by Citus Cloud [0]. I know it's not the same, but you can spin just a single worker and essentially end with a faster PG than the vanilla PG. [0] https://www.citusdata.com/product/cloud

It starts at a minimum of 2 workers. And the pricing is steep too. The workers only operate on distributed tables so if you can't shard your data then you won't get any use out of those nodes, and sharding comes with its own problems. Citus isn't recommended unless you really need the size and want to stick with Postgres/OLTP.

Re: Digital Ocean Managed Databases

#53

Post by dewey »

joering2 wrote: post #40
Scarbutt wrote: post #32

Earlier quoted context omitted.

This is bad, but your data should have also resided somewhere outside DO.

I was only technical adviser for a while, but I know they did offsite backups but its hard to have these up to a minute. So they tried to recover the latest version of their DB so that truly no records are missing. Edit: my original post got downvoted severely in few minutes from posting. Hello DigitalOcean staff and/or owners!

I think more background information would be more appropriate than conspiracy theories of what happened to you. Usually there are two sides to a story.

Re: Digital Ocean Managed Databases

#54

Post by timdev2 »

ZWoz wrote: post #37
nerdywordy wrote: post #6

I for one have always liked the simplicity of DO for hosting but I've never wanted to take on the full liability of self-rolling a DB server (and backups and replicas). So everything my company has I've put on heroku or azure. This has potential to be really significant as I'd wager there are a lot of folks in similar situations.

Can you explain it more? Why you think that running your own DB instance is such overhead? Are you ever tried running your own, with mysql/mariadb for example?

Mostly because databases are the key piece o data-persistence infrastructure. Spinning up a MySQL db to dev against, or a single server for a hobby project is quick and easy.

In production, all of a sudden you have a lot of work to do, especially around HA. Figure out replication, get it working, figure out how to monitor/alert if it stops working, figure out failover, figure out how to test that failover actually works, etc.

Support around that stuff has improved over the years, but it's still non-trivial and high-risk to DIY. It's a very different scenario than a stateless app server where you can have easy redundancy.

Re: Digital Ocean Managed Databases

#57

Post by menacingly »

timdev2 wrote: post #54
ZWoz wrote: post #37

Earlier quoted context omitted.

Can you explain it more? Why you think that running your own DB instance is such overhead? Are you ever tried running your own, with mysql/mariadb for example?

Mostly because databases are the key piece o data-persistence infrastructure. Spinning up a MySQL db to dev against, or a single server for a hobby project is quick and easy. In production, all of a sudden you have a lot of work to do, especially around HA. Figure out replication, get it working, figure out how to monitor/alert if it stops working, figure out failover, figure out how to test that failover actually wo…

and unless you're one of the elite few for whom good HA is actually easy, your attempts will likely end up with something that you _believe_ is as available as RDS

Re: Digital Ocean Managed Databases

#58

Post by doh »

brightball wrote: post #48
doh wrote: post #27

Earlier quoted context omitted.

I believe most of those are offered by Citus Cloud [0]. I know it's not the same, but you can spin just a single worker and essentially end with a faster PG than the vanilla PG. [0] https://www.citusdata.com/product/cloud

Isn’t Citus AWS only right now though?

Yes. I meant this more as a hosted solution in general.

Re: Digital Ocean Managed Databases

#59

Post by marpstar »

timdev2 wrote: post #54
ZWoz wrote: post #37

Earlier quoted context omitted.

Can you explain it more? Why you think that running your own DB instance is such overhead? Are you ever tried running your own, with mysql/mariadb for example?

Mostly because databases are the key piece o data-persistence infrastructure. Spinning up a MySQL db to dev against, or a single server for a hobby project is quick and easy. In production, all of a sudden you have a lot of work to do, especially around HA. Figure out replication, get it working, figure out how to monitor/alert if it stops working, figure out failover, figure out how to test that failover actually wo…

For me it isn't even this complicated. I just don't want to have to manage OS/MySQL/Postgres version upgrades or worry about having to troubleshoot when things on the server go south.

Just give me a database to connect to and take my money, please.

Re: Digital Ocean Managed Databases

#60

Post by mountainofdeath »

ZWoz wrote: post #37
nerdywordy wrote: post #6

I for one have always liked the simplicity of DO for hosting but I've never wanted to take on the full liability of self-rolling a DB server (and backups and replicas). So everything my company has I've put on heroku or azure. This has potential to be really significant as I'd wager there are a lot of folks in similar situations.

Can you explain it more? Why you think that running your own DB instance is such overhead? Are you ever tried running your own, with mysql/mariadb for example?

Running your own DB is a recipe for disaster UNLESS you know what you are doing and can invest resources continuously in keeping it up. If you have a good DBA, it probably isn't too much of hassle as long as you scale up with the number of DBs and you have automation to help along the way. However, at that point you are almost to a hosted solution anyway.

For hobby projects, a single self-managed instance is fine. For production in a business critical environment, much more thought needs to go in.

Post reply on HN