CrowdPing. Disrupting uptime monitoring.
I started blogging on www.phphatesme.com after that I founded www.thewebhatesme.com. Both blogs had one thing in common. The “Ideenschmiede”. It was a column where I wrote about ideas I did not have the time to realize.
Today I came across a little idea that could change the whole ping and uptime business. As the founder of www.leankoala.com I am not able to do this on my own at the moment.
But now the idea:
When trying to build a competitor to Pingdom the most challenging part is the infrastructure. You need to provide servers all over the world. How fast is your page from the USA or Europe? Or is it reachable? If you want to check a lot of urls those software a a service providers can get very expensive. Especially for smaller companies.
So what is CrowdPing? The idea behind CrowdPing is to share the infrastructure. If you got a server with some low load just install the tool and you are part of the Crowd. From now on all CrowdPingers can use your server to check if theirs is still online. And of course the other way around.
So if you did ten checks on other domains you are allowed to check your system ten times. If the requested domain/url can not be reached, an e-mail will be send by the client. For a software developer that should be an easy task to implement.
The only thing that is a little bit more complex is the queuing and counting system. Every check someone is performing must be counted and credited. But that can be done with redis that is quite good adding one and queuing events.
What do you thing? Anyone interested in bringing it to live?
