3 ms·
I created this service mainly as an exercise to help me learn more about distributed applications. Behind the simple interface sits a multi-node setup with mult
by uggedal 17y ago
I created this service mainly as an exercise to help me learn more about distributed applications. Behind the simple interface sits a multi-node setup with multi-master replicated Tokyo Tyrant instances for persistence.
I'd appreciate any suggestions or improvements.
- invisible 17y agoFor one, you should mention on the front page a) 15 minute poll-times (then also say "with optional upgrades"), and b) multi-node checks to ensure you know when you are really down.
- dzlobin 17y ago"with optional upgrades" there is your revenue model :-)
- joshuarr 17y agoI'm trying it out. I love it so far. Couple ideas for paid features: - A chart showing uptime vs. downtime. I just like charts. - Ability to display server details like host etc. - Optional notifications via cell phone text - Ability to auto-notify hosting service via email of the downtime.
- uggedal 17y agoGlad you're liking it. I have most of these features written down as possible improvements and/or premium features. But it's good to get some validation of my own crazy ideas.
- joshuarr 17y agoI'm getting a lot of error notices of no response before five seconds, then immediate error resolved. Not sure what this indicates. As I'm just a designer, I don't know if this is a problem or not. I'm at the point where I ignore all the notices. So now if it did really go down I wouldn't believe it.
- uggedal 17y agoThanks for the feedback. I'll probably increase the max timeout.