What are our standards for hosting providers? #5
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
spoons.technology/plots#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there anything we do/don't want in a provider? Ethics/scale/location?
Do we need to have IPv4 everywhere - if only to avoid cutting off the rest of our network
"Not in the US" feels like an obvious one, and make sense from a latency PoV anyway, assuming the user base will likely be mostly European.
The EU seems to be intent on matching the UK and US on Orwellian online regulations, but it we exclude it that doesn't leave many options!
Aside from that, IPv6 support is an obvious requirement - I'd hope there weren't many places not offering it these days, but worth checking.
Something not mentioned in the OP - do we use "high level" services (like database aaS) or just VMs ?
Maybe on the "where is data?" thing, we should aim for being able to easily move? Not sure I can point at a specific place and call it fine. Perhaps also, "make sure we can flee" makes it just a price/tech question?
v6 seems like something we want, though also at least some v4 - even just enough to connect to the rest of our infra. accessibility thing too - not everyone will have v6
I guess the comments about lock-in in #4 (comment) apply to using our chosen provider's non-VM services too?
Something generic like S3 storage would be fine - pretty easy to migrate if necessary. Anything more custom / provider-specific I'd be much more wary about.
Yeah - non-VM foo feels like the lock-in risk. My thought was pretty much that S3-ish storage would be fine, and probably managed databases.