Re:Healthcare.gov: Code by the People, for the People, Relea...
by digiphile on Tuesday July 09, 2013 @09:25PM
(#6016856)
I can think of any number of blog posts that pack more buzzwords per paragraph than this, but your experience may vary. http://mobile.slate.com/articles/business/moneybox/2013/05/d...
To your substantive point, no one skimped on reliability here. The content was pushed into Akamai precisely so it would always be available, quickly, to end users. Reducing servers in this context isn't skimping -- it's saving money by using modern Web tech. Developing this site also wasn't an option, as your comment implies: the law required its development and deployment. If you'd like public funds directed elsewhere, call your Congressional representatives.
"We knew there were performance and reliability benefits from building the stack on HTML."
I know there are performance and reliability benefits from talking in English.
"You're just talking about content. There just needs to be one server. We're going to have two, with one for backup. That's a deduction of 30 servers"
I'm very happy the government decided to skimp on reliability for a public healthcare market.
"You can put Wordpress into Amazon but then you'll have problems; it wasn't designed to be a cloud application."
Wait wait wait Wordpress isn't a cloud app? Fuck, someone go tell Hostgator that--apparently it can't be done!
"Notably, the HHS team has been using feedback to drive design choices from the beginning, applying the 'lean startup' model to development."
Wow, even the lean startup namedrop.
I'd be a lot happier if, instead of putting the Obama webdev team on the gravy train, they spent that same money--you know--actually fixing healthcare. As it is they seem to be just doing free advertising and lead generation on the public dime for the insurance companies.