How we've approached reliability & cost savings for our strapped SaaS

1

QuestDB

We've come a long way from my first iteration where I ran speedtest-cli in a docker container that posted data to mysql all hosted on a single ec2 instance in AWS, with absolutely no fault tolerance or scaling. Now we host our stack in containers running in GKE, split into their own microservices, passing data between our services using pubsub, and using a bad ass new TimeSeries database QuestDB. Additionally, our team has rewritten our local client in Go which allows us to run on just about any kind of device / OS -- broadening our market to so much more than folks wanting to measure their internet from their PC at home.

#Time Series Database #Databases #Developer Tools 19 social mentions

2

WinSW

We use a third party library (winsw) to package our exe as a windows-serice.

#Monitoring Tools #Command Line Tools #CRM 11 social mentions