3 ms·

100%. The hidden part here is "DigitalOcean-level of complexity" is actually "DigitalOcean-level of features." The big cloud providers have a variety of offeri

100%. The hidden part here is "DigitalOcean-level of complexity" is actually "DigitalOcean-level of features." The big cloud providers have a variety of offerings of different complexity. Using GCP as an example: want k8s with all it's flexibility and complexity? You have GKE. Want to still run containers, but abstract away all the cluster resource management? CloudRun. Abstract away the container itself? CloudFunctions. AWS has EKS, ElasticBeanstalk, etc. I understand people get overwhelmed the first time they're dropped into the console of these cloud providers but really it just takes a bit of reading to figure out what you should/shouldn't care about. And the benefit of doing so is enormous.

deleted 5y ago
[deleted]
sdoering 5y ago
Disclaimer: Anecdata Privately I host nearly everything on a shared host in Germany (that is everything I can host without sudo) [1]. For company policy reasons I must absolutely use AWS or GCE. For an internal project I need to setup Matomo. Something I did thrice in the last few month on [1]. OK login through SSO into AWS. Look around, ask Google, find the bitnami image, click few buttons. Done. OH shit. Now I need to somehow make it publicly available. OK. Google again. Ah this is the way. Few hours of reading and clicking later I have a publicly reachable Matomo instance. Oh hey. It warms me that it is not ssl encrypted. OK. How to do let's encrypt? Google again with my second batch of coffee (or was it the third). Found an easy way, just enter a command in the shell. Oh hey, how do I get my ssh pub key into my EC2 instance? Damn the day is nearly gone and I have yet to deliver this tangential asset to an internal project while killing my CCI (how much I am booked on client work) for something that the first time took me 30 minutes with the great documentation from [1]. To me as a meager Data Analyst the complexity of cloud offerings is a nightmare. And the documentation is written for other echelons of tech understanding most of the time. [1] uberspace.de
- burnoot 5y ago
  If you’re a data analyst, then of course infra and sysops activities on cloud seem complicated. I’m sure a sysadmin could run/write sql, but would find the rest of your domain complicated too.

deleted 5y ago

[deleted]

sdoering 5y ago

Disclaimer: Anecdata Privately I host nearly everything on a shared host in Germany (that is everything I can host without sudo) [1]. For company policy reasons I must absolutely use AWS or GCE. For an internal project I need to setup Matomo. Something I did thrice in the last few month on [1]. OK login through SSO into AWS. Look around, ask Google, find the bitnami image, click few buttons. Done. OH shit. Now I need to somehow make it publicly available. OK. Google again. Ah this is the way. Few hours of reading and clicking later I have a publicly reachable Matomo instance. Oh hey. It warms me that it is not ssl encrypted. OK. How to do let's encrypt? Google again with my second batch of coffee (or was it the third). Found an easy way, just enter a command in the shell. Oh hey, how do I get my ssh pub key into my EC2 instance? Damn the day is nearly gone and I have yet to deliver this tangential asset to an internal project while killing my CCI (how much I am booked on client work) for something that the first time took me 30 minutes with the great documentation from [1]. To me as a meager Data Analyst the complexity of cloud offerings is a nightmare. And the documentation is written for other echelons of tech understanding most of the time. [1] uberspace.de

burnoot 5y ago
If you’re a data analyst, then of course infra and sysops activities on cloud seem complicated. I’m sure a sysadmin could run/write sql, but would find the rest of your domain complicated too.