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

101–110 of 171 posts

Re: Digital Ocean Managed Databases

#101

Post by jarland »

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…

The answer depends on a variety of factors, but in general, when we're alerted to something that could be a violation of our Terms of Service, we attempt to engage with customers. In some cases, we may take actions against the resources running against an account and a vast majority of the time, there is a grace period before any permanent action is taken. If you have questions about specific cases, we recommend contacting our support team directly.

Re: Digital Ocean Managed Databases

#102

Post by geetfun »

raiyu wrote: post #95
donmcronald wrote: post #88

Earlier quoted context omitted.

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…

@raiyu, this is excellent and thank you. It’s reassuring to see DO’s leadership come out and explain things.

Re: Digital Ocean Managed Databases

#103

Post by nnq »

virmundi wrote: post #100
nnq wrote: post #92

Earlier quoted context omitted.

...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.

...yeah, but if best value for money would be the absolute goal, DO itself is quite expensive compared to Hetzner or Linode last time I compared. Others like OVH or Scaleway could be even cheaper.

Re: Digital Ocean Managed Databases

#104

Post by ljosa »

How is DigitalOcean's resilience to DDoS attacks? After Linode's giant DDoS-related outages a couple of years ago, I moved everything to AWS on the theory that they (along with Google and Azure) would be better at mitigating similar attacks. Would be nice to have DO as an option.

Re: Digital Ocean Managed Databases

#106

Post by raiyu »

whitepoplar wrote: post #24
joering2 wrote: post #21

Earlier quoted context omitted.

Glad you are having fun working on your after hours side project with DO. But please DO NOT host with DO if you plan to run a real production systems, build a company, hire people etc. I have never found a better company to spun off a server and play with some settings but when their algorithm decides there is something fishy, bye bye your account, servers, backups, you never going to see any of this ever again. The…

This is frightening. Can anyone from DO chime in?

Just making sure to reply to each person that raised a concern. There is a lot of fraud that comes into every single cloud provider as root access to a virtual server can be used for a lot of malicious activity. As a result every cloud provider has automatic and manual processes that they run to find these accounts and flag them.

In the case of DigitalOcean when an account is flagged it is locked, which simply prevents a user from creating more resources and an email notification goes out to the user to establish a line of communication.

There is no service interruption, and certainly the account, it's droplets, and other resources are not deleted, and never deleted automatically when the account is initially flagged.

There are numerous communications that go out even if a user is unresponsive.

Re: Digital Ocean Managed Databases

#107

Post by StudentStuff »

nnq wrote: post #103
virmundi wrote: post #100

Earlier quoted context omitted.

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.

...yeah, but if best value for money would be the absolute goal, DO itself is quite expensive compared to Hetzner or Linode last time I compared. Others like OVH or Scaleway could be even cheaper.

DigitalOcean and Linode are currently the same price, what $5 buys you on DO gets you the same specs on Linode.

Hetzner is not a reasonable choice for servers IMO, its akin to hosting in a datahole in Dallas, expect mixed bandwidth quality and questionable policies when issues arise. Comparatively, OVH looks stable.

Scaleway doesn't take abuse reports seriously FYI, these attacks are still primarily coming from IPs announced by their ASN, over a year after this article was written: https://badpackets.net/ongoing-large-scale-sip-attack-campai...

Re: Digital Ocean Managed Databases

#108

Post by JonoBB »

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.

The performance on Lightsail is bad compared to DO - CPU, network, disk access are all much slower at similar price levels.

Re: Digital Ocean Managed Databases

#109

Post by Something1234 »

ljosa wrote: post #104

How is DigitalOcean's resilience to DDoS attacks? After Linode's giant DDoS-related outages a couple of years ago, I moved everything to AWS on the theory that they (along with Google and Azure) would be better at mitigating similar attacks. Would be nice to have DO as an option.

Wait I thought AWS made you pay if you got hit with a DDoS or even a moderate amount of traffic. It's just there is no cap on costs if you have any kind of autoscaling enabled. There use to be many posts complaining about surprise charges on AWS.

Re: Digital Ocean Managed Databases

#110

Post by ryanianian »

sdegutis wrote: post #12
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.

If you have a relatively small set of users, setting up your own database is usually as simple as setting it up locally and you won't need shards or anything. And setting up backups is as simple as adding a cron job that calls your backup shell script, which you can test separately. And by "small set of users", consider what SQLite's own website[1] says: Generally speaking, any site that gets fewer than 100K hits/day…

SQLite doesn't really have concepts like replication (HA) or concurrent writers.

Notably, the SQLite website is (as far as I can see) read-only. So it's great if all you need is a SQL read API atop your structured data (and 100k hits/day is probably only limited by the filesystem/os since SQLite isn't a server). But you're setting yourself up for headaches by using SQLite if you need simultaneous read/writes combined with HA.

Post reply on HN