Despite the fact that we already have multiple queueing and caching systems running for gladlyCast, the last few days we have also seen gladlyCast went down for a few minutes a few times.

Well, that has taught us one thing:
Queuing and caching systems are only good for ensuring minimum or zero lost of tweets (all your text messages are always accounted for), it, however, doesn’t help in ensuring minimum system downtime.

For that, we have just written an extensive monitoring daemon, almost similar to that of Apache HTTP Server, to ensure that gladlyCast is up most of the time.

Sorry for the pretty technical post. We promise we will not do this often. If you do not get it, fret not, it simply just means we have just greatly increased the reliability of gladlyCast.

By the way, do stay tuned. We have some announcements to be made very soon.