> As a startup you are typically better served by a DigitalOcean-level of complexity, and there are plenty of such offers in the EU (Hetzner Cloud, Gridscale, OVH, etc)
As an actual startup founder who started as a 1 man startup, strongly disagree.
Spent maybe $200 a month on Google Cloud, got an actual production ready cluster. Scaled up to Millions in revenue, never had to deal with any Linux Server admin BS.
More time on business, less time on Linux Sysadmin.
> never had to deal with any Linux Server admin BS.
Oh, you just had to deal with a different flavor of BS. Or you was lucky and everything just worked out for you (but why Google Cloud and not some PaaS like Heroku, so you don't have to deal with cloud infrastructure/servers BS altogether?)
I've been both a system administrator, managing GNU/Linux and FreeBSD servers in the ancient ages, and DevOps guy doing all sort of stuff in the clouds. The complexity is still there, it hadn't disappeared in some magic cloud pixie dust, even though sales would wanna tell you that fairy tale. But here's the thing - you never get to dive into those waters (or hire someone to do it for you, be it an employee, contractor or paid support) unless shit hits the fan and forces you to.
You must've cheerfully walked through a minefield and haven't stepped on and even seen any mines. Honestly, I'm happy it worked that way. And hopefully, this minefield is sparse enough those days so you're a rule not an exception - I don't have meaningful statistics. It would be actually interesting to run a poll or something. I just happen to have seen a few companies/people for whom clouds weren't all unicorns and rainbows.
And as for the flavors - it just happened that you knew how to set up stuff in Google Cloud. Would you happened to know how to spin a simple instance on Digital Ocean instead and went that way, and be lucky to not encounter any serious issues, it would've been the same painless experience, just different flavor.
My server load was not the size I needed 20 dedicated servers, but far too much for Herkou. Just running a 120 core 24/7/365 on heroku is like.. all of my revenue. (Vs 1% on google cloud and maybe .1% on hertzer).
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.
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.
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.
Yes, OVH experienced force majeure episode. I didn't follow exactly how the compensation was rolled out. I know it was messy. I am not going to defend their actions, I am sure they could always handle this better.
Disaster recovery planning is practice we should all adhere to. Hindsight is 20/20. Not trying to be a smartass. I know it was painful for a lot of folks.
At the same time, unless you paid for managed service with clear SLAs, then responsibility is yours.
And power to you. You did what you though was best in your circumstances.
Today circumstances have changed. You need hassle free scalable DB, then AWS RDS might you best choice. Maybe.
You need open standard IaaS, well, there is ton of options.
Even before K8S, you had and option of Openstack with Ansible. Yes, very different beast, but still much _simpler_ and _cheaper_ than stocking on large number of IT professionals.
We colocate about 20 servers and in any given month, spend no more than 1 person-days worth of time dealing with it. Many months we spend no time. That includes both sysadmin and hardware. But this requires knowledge that most devs these days probably don't have.
We might spend more time messing around with AWS than our colocated servers.
Right, if you legit need 20 servers than it might make sense for you. I would fit on like 2-3 decent sized servers if I did co-___location, and would save not even 1 developer-day of salary...
I would guess that if costs is an issue then it must also be balanced compared to the potential profits. If your current $200 solution only allowed you to have US customers, while a $300 solution would allow you to have both US and EU customers, which one would you choose?
>I would guess that if costs is an issue then it must also be balanced compared to the potential profits. If your current $200 solution only allowed you to have US customers, while a $300 solution would allow you to have both US and EU customers, which one would you choose?
Whichever one let me pay rent at the end of the month
That seems good. Someone could copy your business and spin up on the EU market. If its profitable its profitable and its no worry for you. If its not profitable then the EU market is not large enough to carry the product on its own. GDP of the US is around $25 trillion, and EU is around $18 trillion, and population wise there are around 300 million people in the US and 400 million people in the EU.
Might I ask you what kind of product your 1 man startup have?
I am not 1 man anymore, we grew up a bit. But we are an ecommerce platform, basically centered around the big US marketplaces (Amazon, eBay, walmart.com). Yes Amazon and eBay are in Europe, so we are there.. but no say UK or France specific markets at this time.
Just make sure your BCP plan includes other provides. HN is full of stories where peoples' accounts are blocked with no reason and without means of effective contact.
Tangential, but assuming you're talking about Listing Mirror? I considered working on a similar product a few years ago, but felt the market was too competitive. Interesting you were able to compete with the plethora of similar services.
From day 1, you KNOW there is demand for your product. You can look up Channel Advisor and see the revenue. And 20 smaller companies under fighting for the rest.
Cons of course being, you have to figue out how to compete with all of these guys ;)
As an actual startup founder who started as a 1 man startup, strongly disagree.
Spent maybe $200 a month on Google Cloud, got an actual production ready cluster. Scaled up to Millions in revenue, never had to deal with any Linux Server admin BS.
More time on business, less time on Linux Sysadmin.