Live data from Hacker News

What One-person SaaS Healthchecks.io uses for hosting, hardware and software

blog.healthchecks.io

31–40 of 180 posts

Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software

#32

Can you share more details about what the 4 HAProxy servers are doing? I run a SaaS too, but on a single beefy machine handling web and DB stuff. I'm curious what I'm missing out on not using HAProxy in front.

To answer the question of why four of them:

* the traffic from the monitored systems comes with spikes. Looking at netdata graphs, currently the baseline is 600 requests/s, but there is a 2000 requests/s spike every minute, and 4000 requests/s spike every 10 minutes.

* want to maintain redundancy and capacity even when a load balancer is removed from DNS rotation (due to network problems, or for upgrade)

There are spare resources on the servers, especially RAM, and I could pack more things on fewer hosts. But, with Hetzner prices, why bother? :-)

Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software

#33
post #30

Earlier quoted context omitted.

> This is just slightly more complex than a static site That's because their product is only slightly more complex than a static site. I wish every project was as basic as a web server and database but it's pretty rare these days.

> I wish every project was as basic as a web server and database but it's pretty rare these days. I feel like the overwhelming majority of web based software projects can be catered for with exactly this setup. If it's rare it's because everybody's drunk the Kool-aid

Maybe in the past, sure. But these days people rely far more on their web apps.

Having a 1-2 day outage because your architecture is not highly-available across data centres like this one just doesn't cut it. And multi-day outages are very much real because of the thundering herd effect as companies rapidly try to move between data centres exhausting capacity.

And much of the complexity in modern day architectures come from high availability and security.

Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software

#35

What volume of data are you storing in postgres? Any reason not to use a hosted postgres provider? At first glance it seems like a lot of compute for the service but curious about scale

Around 200 write tx/s as a baseline. Spikes to 2000 write tx/s at the start of every minute, and 4000 write tx/s every 10 minutes.

> Any reason not to use a hosted postgres provider?

* Cost

* Schrems II

* From what I remember, both Google Cloud SQL and AWS RDS used to have mandatory maintenance windows. The fail-over was not instant, so there was some unavoidable downtime every month. This was a while ago – maybe it is different now.

Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software

#36
I respect that they use a combination of git tools just for version controlling. I understand that you can do everything with the git cli but my experience is that the more I tried to limit myself to the cli the messy my version controlling become.

Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software

#38
>A dedicated laptop inside a dedicated backpack, for dealing with emergencies while away from the main PC.

This line here shows much thought has gone into "what if...." situations. Bravo!

I too have a similar setup - I have a contractual responsibility to my clients, and if anything goes wrong with my main equipment, I can resume ASAP. This includes a dedicated smartphone for hotspotting if my internet connection dies.

Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software

#40

Question for OP. For the healthcheck's integration solution (email, signal, discord....), how did you go about doing that? I would love to hear about all that. I did find a section about Signal's integration.

Started with just the email integration, and added other integration types over time, one by one. A few were contributed as GitHub PRs.

The Signal one took by far the most effort to get going. But, for ideological reasons, I really wanted to have it :-) Unlike most other services, Signal doesn't have public HTTP API for sending messages. Instead you have to run your own local Signal client and send messages through it. Healthchecks is using signal-cli: https://github.com/AsamK/signal-cli

Post reply on HN