the progression from Heroku to AWS is very common as SaaS businesses grow. However one thing that’s missing from all “alternatives to Heroku” is what I call life after deployment or Day-2 operations. Many solutions show you a sleek demo of how easily you can deploy a Hello World app to their platform but leave you in a straight jacket when it the app is deployed and you need tools to keep it running, like changing an…
vercel is great
11 years of hosting a SaaS
41–50 of 222 posts
Re: 11 years of hosting a SaaS
#42> Use managed services for as long as possible Big agree here. Yes, you can save stupid money by handrolling postgres on an extremely beefy Hetzner server, or you can pay someone else and keep building your product: https://onlineornot.com/self-hosting-vs-managed-services-dec... This isn't to say, "don't bother learning how to do it yourself", but more "learn to pick your battles".
It may be a generational thing, a matter of familiarity with computing and computers. For someone who's lived through the 80s, "handrolling postgres" doesn't sound nearly as scary as you imagine. I expect the cost/benefit analysis of "handrolling postgres on a beefy Hetzner server" vs "navigating the menus and options of AWS services" would be different for different teams.
Kubernetes, "Argo CD", zero-trust, the sheer amount of "management" is off the chart.
"Installation of kube-prometheus-stack helm chart".. "Installation of openebs-zfspv"..
It's not postgres that's the problem here.
Re: 11 years of hosting a SaaS
#43Earlier quoted context omitted.
It may be a generational thing, a matter of familiarity with computing and computers. For someone who's lived through the 80s, "handrolling postgres" doesn't sound nearly as scary as you imagine. I expect the cost/benefit analysis of "handrolling postgres on a beefy Hetzner server" vs "navigating the menus and options of AWS services" would be different for different teams.
I'm looking at the ansible playbooks to setup my favourite beefy baremetal Hetzner server (128GB ram, Ryzen 9 5950X 16-Core, 450Gb fast NVME SSD, 3.5TB x2 NVME SSDs, 155€/month): - Install Debian 11 while booted in rescue mode. - Setup the root file system encryption using cryptsetup and dropbear (to enter the key during the boot through SSH). Involves chroot and some fun commands. - Setup ZFS encrypted mirror filesy…
Re: 11 years of hosting a SaaS
#44Infrastructure is kind of a solved problem for common use cases today, just requires the expertise.
With our ducks in a row I'd next have look to a GRC function for the compliance bits whilst splitting the platform engineers time between embedding engagements and tooling investments.
You're on the right path man, I'd love to know what I know now back then but unfortunately time doesn't work like that.
Re: 11 years of hosting a SaaS
#45I'm sure its interesting but I am making a conscious choice to not read or linger on user hostile articles. As soon as I want to scroll I am interrupted by a page takeover requiring action and subsequently compelling me to lose interest. Did you want me to read it or click buttons for you? Too bad your UI gets in the way of the U.
Re: 11 years of hosting a SaaS
#46So what are the new Herokus? What do you recommended for starting a serious project? AWS AppRunner? How about something open source?
Azure App Service is a thing that everyone just skips over, listing competitors with an annual revenue smaller than some individual Azure App Service deployments... I mean seriously, railway.app has just fifteen employees in total, and revenue in the single-digit millions. Reminds me of when someone posted a "cloud storage vendors poster" with hundreds of vendors -- but not Azure -- some with revenues smaller than th…
Used it for a few clients but it's tough to keep using it with all the issues, so I'm looking at Render and other alternatives. But if Railway could smooth out the reliability / stability, I wouldn't have any reason to switch.
Re: 11 years of hosting a SaaS
#47I'm sure its interesting but I am making a conscious choice to not read or linger on user hostile articles. As soon as I want to scroll I am interrupted by a page takeover requiring action and subsequently compelling me to lose interest. Did you want me to read it or click buttons for you? Too bad your UI gets in the way of the U.
Substack is definitely scummy in this regard, it's not really the author's choice (although a conscious decision was made to host it on Substack).
I guess they do it because it works, and if the average person felt the same way, they wouldn't be doing it?
Re: 11 years of hosting a SaaS
#48Earlier quoted context omitted.
It may be a generational thing, a matter of familiarity with computing and computers. For someone who's lived through the 80s, "handrolling postgres" doesn't sound nearly as scary as you imagine. I expect the cost/benefit analysis of "handrolling postgres on a beefy Hetzner server" vs "navigating the menus and options of AWS services" would be different for different teams.
I don't think "modern" stacks are sane enough to "handroll" anymore. Sure, you can do it, but look at the poster in this thread that details the setup of a debian server. Kubernetes, "Argo CD", zero-trust, the sheer amount of "management" is off the chart. "Installation of kube-prometheus-stack helm chart".. "Installation of openebs-zfspv".. It's not postgres that's the problem here.
Many of the problems these tools solve are problems that wouldn't exist building things the old fashioned way. If you stick relatively close to the metal, operating this stuff is pretty easy.
However it's notable that a very valid reason to prefer managed services as a SaaS is to cover your ass if things go wrong. Your SLA violation is their SLA violation.
Re: 11 years of hosting a SaaS
#49Earlier quoted context omitted.
It may be a generational thing, a matter of familiarity with computing and computers. For someone who's lived through the 80s, "handrolling postgres" doesn't sound nearly as scary as you imagine. I expect the cost/benefit analysis of "handrolling postgres on a beefy Hetzner server" vs "navigating the menus and options of AWS services" would be different for different teams.
I'm looking at the ansible playbooks to setup my favourite beefy baremetal Hetzner server (128GB ram, Ryzen 9 5950X 16-Core, 450Gb fast NVME SSD, 3.5TB x2 NVME SSDs, 155€/month): - Install Debian 11 while booted in rescue mode. - Setup the root file system encryption using cryptsetup and dropbear (to enter the key during the boot through SSH). Involves chroot and some fun commands. - Setup ZFS encrypted mirror filesy…
Re: 11 years of hosting a SaaS
#50Earlier quoted context omitted.
I had the same experience with some backend engineers, they constantly looked down on the front-end engineers, ridiculing JavaScript and CSS. And while all those frontend engineers picked up backend languages and became fullstack developers. Those backend engineers couldn't do the most basic frontend things to save their lives.
Meh. FE, BE, system, embedded; they all go deep. A good engineer can learn one or more in any order, but only fools look down on a discipline they don't understand.
And additionally to this during the time it became viable a lots of FE folks still had to continue battling IE6 in their daily lives so online documentation still lagged and had a clear smell of the cargo-culting. Heck even today you see people complaining about Javascript here on HN.
But being left behind today, you gotta blame yourself. Early realtime Google-suggestions using AJAX came already back around 2005 (?) and if you didn't take notice and still missed people were doing decent realtime games by 2010 you were doing your best to live under a rock.