37Signals benchmarks uptime vs five leading webapps • Hacker News Board

Re: 37Signals benchmarks uptime vs five leading webapps

#31

Post by functionform » Tue, Jan 31, 2012, 9:12 PM UTC

dhh wrote: post #26

Warry wrote: post #17

Looks like 37signals changed a bit in 6 years : http://37signals.com/svn/archives2/dont_scale_99999_uptime_i...

We certainly have! I would be embarrassed if we hadn't. Also, that's why we're comparing uptime against big, established web applications. I would not hold these standards up to a 1 year-old, newly started business. You have far more important things to worry about than getting an extra 9 on your uptime.

The newer organizations on your blog spot don't seem to have problems meeting a similar uptime to you guys. Doesn't sound like this holds true anymore.

Re: 37Signals benchmarks uptime vs five leading webapps

#32

Post by dspillett » Tue, Jan 31, 2012, 11:36 PM UTC

verelo wrote: post #18

This is one of those posts that drives me a little crazy :P We recently started a web monitoring company (in beta) http://www.verelo.com to tackle situations just like this. Pingdom monitors every 60 seconds, its just not enough if you want to make claims like "we were only down for 6 minutes". If you want to make claims at a single digit minute level you need to check more regularly, and your checks need to be robus…

Looks useful. I've got a long-poll based monitor part written that I must get into a sensible state and chukc on github at some point. I was intending for it to monitor a few bits of mine in a semi distributed manner (each f my little bits of the net monitoring each other. The long-poll would mean I could "tick" every tens seconds (or even every second, though 10 was the plan) using very little bandwidth (it wouldn't have to be polling a web server either, but in all my cases it would be with the web server doing other local checks (Is the DB up?, Can I login?, No new errors in the critical-stuff log?, ...).

I might have to give your service a look until I finish my little toy, if I ever do.

Re: 37Signals benchmarks uptime vs five leading webapps

#33

Post by skrish » Wed, Feb 01, 2012, 2:49 AM UTC

smackfu wrote: post #15

jiggy2011 wrote: post #13

Earlier quoted context omitted.

Even if they enforced a password change it wouldn't help if they are storing them in plaintext.

A one-time password is usually generated and emailed, then hashed and stored, so not generally stored in plaintext.

It is called a one time password for a reason. Since it has been sent out via some medium in plain text, it is a good practice to force change password on next login.

Re: 37Signals benchmarks uptime vs five leading webapps

#34

Post by verelo » Sun, Feb 05, 2012, 7:50 PM UTC

mrcalzone wrote: post #22

verelo wrote: post #18

This is one of those posts that drives me a little crazy :P We recently started a web monitoring company (in beta) http://www.verelo.com to tackle situations just like this. Pingdom monitors every 60 seconds, its just not enough if you want to make claims like "we were only down for 6 minutes". If you want to make claims at a single digit minute level you need to check more regularly, and your checks need to be robus…

I use Pingdom, but wish they could monitor more frequently for exactly the reasons you mention. In theory my site can be unavailable for several seconds each minute, without showing downtime in the stats. I signed up for your service, but looks like it is invite only right now?

I think most peoples invites have been approved at the moment.

We have a big release scheduled for Feb. Some cool new features like custom useragent strings and PagerDuty integration are going to be pushed out. We're excited :)