Last night there was approximately ninety minutes of intermittent service from FeedDigest which caused a few problems for many users. The service was fully up and running again pretty quickly, but obviously there was an impact. I am still investigating the cause of the problem.
The new proxy system is an interesting one. From a year of RSS Digest, and now Feed Digest, I've learned that having 24/7 rock solid service delivery is of utmost importance, especially when you have paying customers.
At FeedDigest's level though, it's not viable to have rooms full of servers (not just yet anyway!) running the heavy-load FeedDigest software. It is certainly viable, however, to have multiple lighter systems in place to act as proxy/caches to FeedDigest. We'd simply associate app.feeddigest.com with a round robin DNS so that a random proxy/cache server is hit for each request, and then that does the talking to the main FeedDigest servers. In that way, the service never appears to be down, even if a backend server is! The 90 minutes of issues yesterday have underlined that this should be high on the priority list now. Thanks for your support, notifications, and help in troubleshooting.
Secondly, keep your eyes on this blog for a major announcement in the next few days. Yes, FeedDigest is about to hit the big time. It was all signed and sealed several days ago, and it's almost ready to go public..