As a customer I can highly, highly recommend Cronitor. The service is continually improving and the customer support has been second-to-none, they have gone above and beyond to meet my needs.
[deleted]
Growing a cron job monitoring side project into a real business
11–20 of 31 posts
Re: Growing a cron job monitoring side project into a real business
#12Earlier quoted context omitted.
I don't exactly remember how I first came across Cronitor (I thought it was IH, but I guess not), but you guys have been a big inspiration for me as I've been attempting to bootstrap my own side project into a business.
That is really great to hear. Keygen is looking polished!
Appreciate that! Looking to fully launch within the next month or so. :)
Re: Growing a cron job monitoring side project into a real business
#13Loved reading the article. I can really feel the authors/founder's sincerity in giving non-fluff answers.
Re: Growing a cron job monitoring side project into a real business
#14[deleted]
Re: Growing a cron job monitoring side project into a real business
#15Loved reading the article. I can really feel the authors/founder's sincerity in giving non-fluff answers.
I agree. Absolutely fantastic piece and a real encouragement to the rest of us who want to live that dream. I wish you guys the best for the future: you remind me a lot of a company I used to work for called Red Gate. Keep this up and I reckon there's a good chance you'll be making hundreds of thousands a month in five years' time.
Re: Growing a cron job monitoring side project into a real business
#16I'm curious, how does Cronitor actually monitor that the URLs were pinged at the correct times or at all? Part of me thinks they are using cron to check statuses?
Re: Growing a cron job monitoring side project into a real business
#17I'm curious, how does Cronitor actually monitor that the URLs were pinged at the correct times or at all? Part of me thinks they are using cron to check statuses?
We built a python daemon that owns a shard of monitors, iterates them, reads recent history, and dispatches alerts when appropriate. The key things I thought were important when it was built were:
- stateless (needs to be able to be arbitrarily restarted at any time)
- fast (we need to be able to send alerts right when a job fails)
- simple (we will run pings thru a series of simple evaluators where test coverage is easy)
Re: Growing a cron job monitoring side project into a real business
#18Cronitor is great. A few months back I used cronitor for a use case that ended up hitting their ping endpoint at about 10-15 QPS, and they said there was some capacity constraint they were running into (not exhausting though). I would love to hear more about the architecture behind cronitor.
Re: Growing a cron job monitoring side project into a real business
#19This was a really great and inspiring interview. Thanks! I especially liked the "JIT mindset" idea!
Re: Growing a cron job monitoring side project into a real business
#20I'm curious, how does Cronitor actually monitor that the URLs were pinged at the correct times or at all? Part of me thinks they are using cron to check statuses?
We built a python daemon that owns a shard of monitors, iterates them, reads recent history, and dispatches alerts when appropriate. The key things I thought were important when it was built were: - stateless (needs to be able to be arbitrarily restarted at any time) - fast (we need to be able to send alerts right when a job fails) - simple (we will run pings thru a series of simple evaluators where test coverage is…
Interesting! This type of infrastructure and coding fascinates me, thanks for sharing!