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

91–100 of 171 posts

Re: Digital Ocean Managed Databases

#91

Post by plainOldText »

thecus wrote: post #74
plainOldText wrote: post #49

Earlier quoted context omitted.

These are some serious allegations. If this is true then DogitalOcean needs to explain themselves. I guess, one should also have backups off site. Relying on just one provider constitutes a single point of failure.

I suspect that any cloud provider has enormous amounts of fraud on it and no tooling is 100% error free. It's also important to note that GDPR has specific exemptions for companies responding suspected security/fraud related issues. I love DO because the performance for the price is great. Also have no issue supporting emerging tech companies with cultures I connect with.

No question fraud exists on all these platforms, however, if anyone is wrongly flagged by an algorithm, reaching out to the company must be followed by a prompt and timely response, so any misfortune can be remediated. I would assume fraudsters wouldn't typically reach out to have their accounts reinstated.

In the digital age, startups and businesses rely on cloud providers for their livelihood. These providers must be reliable and trustworthy, otherwise they shouldn't get a penny.

Also, I'm not intimately familiar with OP's situation, my comments are just common sense generalizations; I think!

Re: Digital Ocean Managed Databases

#92

Post by nnq »

tracker1 wrote: post #76
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.

I was literally going to spend the weekend testing latency between the US DO data centers and VMs on Azure and AWS just to see if any were pretty reasonable (consistently under 10ms) so I could use DO for my application and Azure or AWS for the DB hosting and management. This is incredibly great timing.

...then why not just use AWS's Lightsail instead of DO so you can use AWS RDS without worrying about latency? (Or the equivalent for Azure or GCP.)

Really asking, bc for next personal projects I was getting ready to abandon DO and use AWS Lightsail + RDS.

Re: Digital Ocean Managed Databases

#93

Post by raiyu »

drchiu wrote: post #73
jarland wrote: post #67

Earlier quoted context omitted.

Hey friends! My name is Jarland and I'm on the support team at DigitalOcean. We do have a number of fraud and abuse algorithms, and when we are alerted to potentially fraudulent activity, we take appropriate action, which includes notifying and communicating with individual users. I also want to confirm that we are fully compliant with GDPR.

Thanks @jarland for chiming into this thread. I love how DO has evolved over the past several years and want to comment about that. I use DO for production and have gradually migrated my infrastructure away from AWS and Linode to Digital Ocean as the platform improved. Just a quick question: If the algorithm is triggered (regardless if it is a false positive or not) and the user is notified, what happens with the dro…

Depending on which items are flagged the account is put into a locked state, which means that access is limited. However, the droplets for that account and other services are not affected at all.

The account is also notified about the action and a dialogue is opened, to determine what the situation is.

There is no sudden loss of service. There is no loss of service without communication. If after multiple rounds of communication it is determined that the account is fraudulent, even then there is no loss of service that isn't communicated well in advance of the situation.

Re: Digital Ocean Managed Databases

#94

Post by tracker1 »

mtw wrote: post #69

Would be great to see a benchmark vs a database in a regular DigitalOcean droplet, or information about hardware. This information would be useful for projects requiring high performance per sec.

No details on pricing, but wouldn't be surprised to see the pricing close to matching a droplet, and deploying managed over existing infrastructure. There are of course tweaks I've seen for performance on existing clouds (raiding over block storage devices), tweaking swap space/usage, etc.

Not sure how deep it'll go in the managed usage, but very happy to see it. The one piece I've really felt was deeply missing.

Re: Digital Ocean Managed Databases

#95

Post by raiyu »

donmcronald wrote: post #88
drchiu wrote: post #73

Earlier quoted context omitted.

Thanks @jarland for chiming into this thread. I love how DO has evolved over the past several years and want to comment about that. I use DO for production and have gradually migrated my infrastructure away from AWS and Linode to Digital Ocean as the platform improved. Just a quick question: If the algorithm is triggered (regardless if it is a false positive or not) and the user is notified, what happens with the dro…

Yeah, I want to know if the execution is before or after the trial. Part of DO's appeal to me is the simplicity and predictable (low) cost. It would be really great if they published well defined account termination procedures. Do I get a phone call? An email? Do I get to respond before being disconnected? Is there an appeals process?

As anyone who runs a service that provides full root access to servers understands there is a tremendous amount of opportunity for potential abuse. It becomes a game of cat and mouse to catch the abusers and prevent them from creating numerous accounts which ultimately impact system performance and can lead to potential problems for real legitimate customers.

Those guidelines aren't published specifically because if they were, then the abusers would immediately begin to route around them, so it's meant to be opaque for a reason, but that is against fraudulent use, not legitimate use.

Re: Digital Ocean Managed Databases

#97

Post by joshuatalb »

I’ve been hoping for this for a while. I’m eagerly awaiting access to their Kubernetes service, so this is a perfect compliment to the upcoming service releases.

Also interesting timing too. Amazon Lightsail (the cheaper AWS alternative) is similarly priced to providers such as DigitalOcean, Linode, etc and released their managed database offering the other day: https://aws.amazon.com/blogs/aws/new-managed-databases-for-a...

Re: Digital Ocean Managed Databases

#98

Post by apapli »

thinkshiv wrote: post #34
bonsai80 wrote: post #9

I don't see any mention of the cost. Is that listed somewhere?

Hi there, this is Shiv - I am the VP of Product at DigitalOcean. Thanks for asking about pricing. We are still working out the pricing details. I can tell you it won't be just the cost of the Droplet because this is a managed service with lots of additional features that you would not get with the current Droplet product.

If you can offer some sort of “hobby” plan with a limited I/O and DB size that would be great for hobby projects like what I build. I’ve used RDS before and it is great, but the cost is a bit eye watering when we are talking about less than one user every 10 minutes.

I’ve found Jaws DB works well for my needs (and pricing), but given they are layered on AWS it does feel like I’m still a bit limited - ie it would be good to still access the DB server so I can spin up multiple DBs (pre-prod, production etc), despite my usage being minimal.

If DO can hit a sub $10pm price point (even with severely restricted performance) that would be awesome!

Re: Digital Ocean Managed Databases

#99

Post by raiyu »

plainOldText wrote: post #91
thecus wrote: post #74

Earlier quoted context omitted.

I suspect that any cloud provider has enormous amounts of fraud on it and no tooling is 100% error free. It's also important to note that GDPR has specific exemptions for companies responding suspected security/fraud related issues. I love DO because the performance for the price is great. Also have no issue supporting emerging tech companies with cultures I connect with.

No question fraud exists on all these platforms, however, if anyone is wrongly flagged by an algorithm, reaching out to the company must be followed by a prompt and timely response, so any misfortune can be remediated. I would assume fraudsters wouldn't typically reach out to have their accounts reinstated. In the digital age, startups and businesses rely on cloud providers for their livelihood. These providers must…

We have an entire fraud and safety team whose sole purpose is to deal with these situations. Every account that is flagged is notified. Every account is communicated with and there are always replies sent. Unless a droplet is actively being malicious, such as sending out a DDoS attack, or performing some other sort of determined malicious activity, there is absolutely no interruption in service. The account is locked so that the account can not create more resources, but there is no disruption to the underlying running resources such as droplets and otherwise. The intent here is to establish a dialogue with the user and determine if the activity is fraudulent or otherwise.

Re: Digital Ocean Managed Databases

#100

Post by virmundi »

nnq wrote: post #92
tracker1 wrote: post #76

Earlier quoted context omitted.

I was literally going to spend the weekend testing latency between the US DO data centers and VMs on Azure and AWS just to see if any were pretty reasonable (consistently under 10ms) so I could use DO for my application and Azure or AWS for the DB hosting and management. This is incredibly great timing.

...then why not just use AWS's Lightsail instead of DO so you can use AWS RDS without worrying about latency? (Or the equivalent for Azure or GCP.) Really asking, bc for next personal projects I was getting ready to abandon DO and use AWS Lightsail + RDS.

DO is cheaper for the servers. AWS is nice, but expensive. If you have the money, use it. If you are bootstrapping or willing to take on challenges yourself, DO like environments will save you a lot.
Post reply on HN