[api]

None of them are. There’s no way you could make money doing that in the VPS market especially with the ludicrous bandwidth costs at AWS.

Most VPS providers rent rack space at large colocation facilities in multiple cities. In some cases they locate right next to major peering points for very good peering and very cheap bandwidth.

Vultr in particular is massively underrated and is certainly good enough to use in production.

One caveat though: most of these providers don’t handle sanitization of storage or encryption at rest as thoroughly as the big clouds do. I’d recommend handling your own encryption at rest with these if you have sensitive data. See: Vault, LUKS, etc.

[whateveracct]

Digital Ocean does offer managed Postgres with encryption in transit and at rest. I had a nice experience with their Postgres offering. They also have an S3 equivalent (spaces) and managed Redis.

[dijksterhuis]

nit pick: Spaces is not an AWS S3 equivalent -- compatibility matrix vs. S3: https://docs.digitalocean.com/reference/api/spaces-api/#aws-...

[SOLAR_FIELDS]

I think it’s fair to not call it equivalent because of that, but it’s also fair to acknowledge what is unsupported is pretty power user level stuff for the most part. I used spaces in s3 compatibility for a few use cases and never ran into the problem that what I was trying to do was unsupported. Granted I was not trying to do fancy things, but still.

Some examples of things that I used the S3 compat for that worked just fine:

- terraform backend

- velero backups

- log store for prometheus/promtail

- docker pull through cache

[dijksterhuis]

Yep, for basic object storage via boto3 etc. it mostly works fine. hence why I called it a nit pick.

There are additional interop things like Apache Spark <--> Spaces that don't work like Spark <--> AWS S3 (endpoint URL config issue which I lost the will to sort out as it was quicker to just use AWS S3 :shrug:).

[blowski]

It doesn’t have full feature parity, but as the post you shared says, they “aim for full interoperability with S3”. If you have an S3 client doing basic object storage stuff, it will work fine with Spaces.

[dijksterhuis]

Eh, not Apache Spark <--> Spaces. Doesn't work out the box unlike Spark <--> AWS S3.

See other child comment above. Faster to use AWS S3 instead of trying to fix it (IIRC can't set the endpoint url or something, which is required for Spaces). :shrug:

[blowski]

I appreciate I'm making a "No True Scotsman" point, but Spark isn't really "a typical S3 client doing basic object storage stuff". I'm thinking of your standard web app persisting uploads and static files.