Why build another website uptime monitoring app?
Yes Web Uptime is another website uptime monitoring app. Why, when there are so many decent alternatives, would I bother building a website uptime monitoring app? Good question. Here are some of my reasons:
- It’s a side project and I have no quarrels with it being a side project. I’m not expecting to beat the big boys here, so competition doesn’t really bother me. It’s a “small slice of a big pie” as they say.
- I wanted to build something using Laravel Spark. I use Laravel all the time in my job and Spark looked awesome, so I needed something to try it out on (want to know how I did it? Read this).
- I looked forward to the technical challenges involved (mainly scaling a cron to check hundreds of sites every minute). I also had to replicate the app across different locations to get true “multi-location” monitoring and I wanted to learn how to do this, and how to scale it.
- I wanted to build something that would be easy to maintain. Given that Web Uptime is a side project, I don’t have unlimited hours of time or money to throw at it. So it had to be lean and simple.
- Most of all I wanted to build something that I enjoy. I don’t want it to become a burden to maintain. I want to enjoy building it, learning from it and maintaining it.
As with almost all of my side projects I built it for myself and I currently use it to monitor my own sites. Even if no-one else ever uses it, at least it will provide me with the satisfaction that it’s something I can use and be proud of.