Slashdot Mirror
Ask Slashdot: What Should a Non-Profit Look For In a Web Host?
An anonymous reader writes "We are a large (multi-national) non-profit and currently deal with 503s on a near daily basis. We've worked on this for over a year and the host hasn't been able to figure out how to fix it. We're paying for a managed host and need to evaluate other options. My boss has tasked me with evaluating a new one. I'm the most geeky of the group, so I know the terms, but don't have a sense of what's actually needed to suit our needs. We sometimes have upwards of 1,000 people browsing the site at the same time, so my sense is that we shouldn't need massive amounts of power or bandwidth... but, somehow that's not working on our current host. Can anyone help me get a sense of what types of hosting will best suit the needs of a 'large' non-profit? We're not Facebook, but we're not a mom-and-pop shop. Any help or tips would be fantastic, particularly if you've also selected a new hosting provider in the past year or so. I don't necessarily need actual names (though those would be nice, too) but at least some tips on what makes a huge difference when suddenly a whole bunch of people around the world read an email and want to help out."
Asking for "a hosting provider" is not enough context: what are the technical details - languages / OS / DB / expected load, etc?
Have you done any troubleshooting on why are you getting 503s - are there not enough app server processes / threads? Is your DB blocking things?
1000 simultaneous users isn't much, so unless you're on a thoroughly undersized VPS (or worse, an oversubscribed *shared* host) you should first look at WHY things aren't working. Changing hosting providers won't help if your app is doing stoopid things (loading the entire DB in memory on every request, etc) but it will take a lot of cash and time.
Have you considered that it might be your application crashing or freezing up that is causing the 503 errors? You'd better rule out that possibility before you look elsewhere, because if your company's lousy code is to blame then you'll likely have the same problems wherever you go.
Breakfast served all day!
It says something about the guy asking the question: i.e. he's not someone who first tries to pass himself off as a professional to a company and who then turns around and asks /.ers to do his job for him. Rather, he's likely someone who does not do this for a living, who specializes in something else, but is just the guy who got stuck with the website problem. The margins are often too tight for non-profits to bring in specialists. Plus, hiring a web guy would be likely be a deductible expense for most businesses, but not so for a non-profit. We might conclude, therefore, that he's looking for a solution that is as low maintenance as possible. Perhaps that's the significance of this being a non-profit.
Based on my experience via my wife's work in the state affiliate of a national non-profit, I feel the OP's pain. The non-profit flag is code, and it decodes to incredibly financially tight fisted and technically naive as an organization.
The OP's org likely spent money ONCE to have a professional set up their web presence, without any budget or plan for follow-on maintenance, upgrades, or refactoring. If they thought about it at all, they likely assumed they'd handle these issues with the luck of having someone tech proficient on staff or get someone to donate their time.
Thus, offering what the OP ought to do is a waste of time. It'd be a huge project to write up the justification to spend significant money on this, and the management chain will want to see alternatives have been explored, first.
So, to the OP: your best bet will be to look over the high customer-service ISPs mentioned in these comments. Another alternative is to see if a local college/uni with an IT/CS program has any fourth year undergrads capable enough to be productive as interns.
Luke, help me take this mask off