4 ms·
Sounds like they are trying to fluff their reliability reputation. I develop a web application that is used by schools and just can't entertain the notion of a
by xd 16y ago
Sounds like they are trying to fluff their reliability reputation.
I develop a web application that is used by schools and just can't entertain the notion of anything other than 100% uptime. I take the reliability of my product very very seriously. If one of my customers had a fire at their school and couldn't access our system for registers - that would be us and them up the proverbial creak without a paddle.
I've built up a company (over 7 years now) with a very good reputation for reliability and uptime. Don't assume that just because something is web based it doesn't require 100% uptime.
- iwwr 16y ago100% uptime is as fanciful a notion as risk-free investment.
- xd 16y agoThe point I was trying to make is that if I had that kind of public attitude to uptime, I'd be out of business pretty much overnight. Yeah, 100% uptime is a crazy notion; but something always to be strived for nonetheless.
- iwwr 16y agoTo be strived for, but if you sign a SLA, nobody would be offering you 100% and tell the truth.
- xd 16y agoI've been seeing it offered more and more in recent years for colo ip transit. Just do a quick search for "sla 100% uptime network". Apart from one of the latest colo providers we use I've witnessed downtime with every single one that offered ip transit with a 100% SLA. That's why we use at a minimum 3 geographically distant providers. So far this approach has not let us down.
- cagenut 16y agothats because they stick in the fine print "once a month scheduled half hour outages don't count, also anything under 5 minutes doesn't count"
- xd 16y agoThere should be a law against that. Reminds me of the "unlimited mobile phone internet" plans here in the UK which in the fine print resolve to "fair use policy of 1GB a month) .. why can't companies just call a spade a spade.
- Silhouette 16y ago> why can't companies just call a spade a spade. Slightly off-topic, but in case there's genuine curiosity there: AIUI, most of the advertising standards rulings about "fair use" policies related to Internet and particularly mobile bandwidth were made quite some time ago, when expectations were very different. It is possible that this was not entirely coincidental, and was motivated by the legal teams at major service providers who saw the current situation coming.
- timthorn 16y agoAn SLA should specify penalties for missing the target. You can offer 100% uptime as the SLA, knowing that you'll only hit x%, but if the cost of compensating for 100-x% is less than the value of offering the SLA at 100% it's worth doing. An SLA only ever guarantees commercial remedies, not service availability.
- bitwize 16y agoMah boiiiii, 100% uptime is what all true coders strive for.
- patio11 16y agoKeep in mind that the typical school has substantially less than 40% uptime...
- xd 16y agoNot sure where you are based, but here in the UK schools are rapidly gaining better uptimes. The biggest problem we see is miss-configured proxies playing havoc with https connections. I couldn't say what the average uptime is, but if a school network goes down we normally get an immediate call asking us if there is a problem our end because they use our system so heavily. So at a guess .. at least 98-99% for the majority of secondary schools, but don't quote me!
- patio11 16y agoThey're only actually occupied for about ~30% of hours in the week during the school year, and the hours are usually fairly predictable, which gives one some advantages. For example, if you had a scheduled maintenance window for 5 hours a week every week starting at 2 AM on Sunday, that would blow 98% uptime but no actual user would ever know. (This has saved my bacon a few times, as 2 of the 3 outages of my software were outside of peak hours, so I could count inconvenienced customers on one hand.)
- xd 16y agoWe use to find the holidays a massive advantage. But schools take some of their holidays on different weeks in different parts of the UK so as we expanded we effectively lost these maintenance windows. Also teachers/students/parents access the system from home so we have to keep it running 24/7.
- ZoFreX 16y agoJust because students are out doesn't mean the school isn't occupied! I used to work as a network admin at a boarding school, and there would usually be at least one "off-site" staff member working past midnight each day (and of course, on-site staff 24/7, although thankfully most of them sleep at night), as well as staff coming in at the weekend. Computers have become mission critical in schools now - lessons, paperwork, planning, organisation, telephones, intercoms, security cameras†, locks‡ were all computer-dependent. To date that school network is the most advanced, highest-uptime network I've ever worked on: two server rooms (network continues at almost full capacity with the loss of either) in separate locations and a backup server in a third location. Unplanned outages were basically non-existent, and the loss of any service was very rare and involved lots of people shouting at us :( † Internal only, external were still on tape ‡ I don't mean all the doors open if the network goes down, but the electronic locks were controlled over the network
- rudiger 16y agoAre you sure your web application "just can't entertain the notion of anything other than 100% uptime"? That sounds like a vacuous promise to me. Even telecoms switches are designed with something like 99.9999999% (9 nines) of availability; that's ~30 milliseconds of downtime a year. I'm not criticizing you or your product, but if reliability is critical, it's made explicit with a realistic SLA.
- xd 16y agoI didn't say we provide 100% uptime. We just don't entertain the idea that we may have to settle for less .. simply, we pro-actively monitor our servers and have enough redundancy in place to keep problems under OUR control. We don't pretend, promise or have an SLA that offers 100% uptime.
- arockwell 16y agoWhat is your actual uptime?
- xd 16y agoGood question. We have had 3 incidents in the last 7+ years. The first 2 occurred when we only had servers in one site. 1, http://www.risktec.co.uk/news/business-continuity-%E2%80%93-manchester-service-tunnel-fire-.aspx http://www.risktec.co.uk/news/business-continuity-%E2%80%93-... (lasted days!!) 2, A thunderstorm knocked out the power to our datacenter, the backup UPS and generators both failed to engage. (lasted a day, we also took our business elsewhere) After the 2nd outage we decided to take up additional colo space elsewhere in the country. This has worked for years and any failures in our life datacenter have quickly been switched over to a hot backup datacenter. We have had around a half dozen minor interruptions caused by server component failures ( psu / hard drive). This is because it takes a few minutes to detect the failure and switch over to a backup. 3, The last major failure was with our DNS hosting. They decided to scratch our main zone from there records because of a billing error. Luckily for us it happened on the Friday before a weeks school holiday. Needless to say we took our business elsewhere. I'm sure we have had other instances of downtime I can't remember, but that's pretty much us in a nutshell. No idea what our uptime on paper would be, funnily.
- arockwell 16y agoThat's not too bad. But does that all add up to more than 9 hours a year of downtime? If so, you're already doing worse than 99.9% uptime. I would also bet your uptime is worse than you think if you're not actively measuring it. However, I'm sure it is "good enough". I doubt it is worth spending an order of magnitude more money to get better than 3 9's for your business, which is more or less the point of the article imo. I find the percent availability -> hours of downtime chart on wikipedia to be a really helpful reference for these types of discussions: http://en.wikipedia.org/wiki/High_availability http://en.wikipedia.org/wiki/High_availability
- jcampbell1 16y agoI also develop a web application used by schools. I have no problems taking the system down in the middle of the night for 30 minutes. Schools are quite possibly the most forgiving customers. Their revenues come from the government, so if your app goes down, they are still going to make payroll.
- maukdaddy 16y agoI work in IT for a very large school district, and I have this argument all the time. Aiming for 4 9s or more is just a waste of money. Sure having the gradebook or scheduling app down sucks, but it doesn't matter at a school. Can the teacher still teach if the systems go down? Yes.
- xd 16y agoI've worked in education for over 10 years. 7 of which was on site at one of England's largest secondary schools whilst consulting for schools all over the country. I've had first hand experience dealing with dozens of LA (what you call districts) technical teams that take this kind of attitude and frankly I find it appalling. I remember when schools where trying to bring in electronic registration, and the LA network teams just didn't give a damn about the schools needs. Instead they made there own conclusions as to what the school needed, and to them, having a reliable network so the school could move into the 21st century wasn't one of them. Schools are becoming more and more engaged in technology, and downtime and poorly maintained systems set teachers and the work they do, back. Teachers need to be able to rely on the technology, simple as that, no excuses. You're not expected to reach 100%, but to admit defeat and argue for that defeat is poor form.