4 ms·
"that contractors built a system that could handle 50,000 people using the site at once" There are over 100 million families in the US and they build for 50,00
by ars 13y ago
"that contractors built a system that could handle 50,000 people using the site at once"
There are over 100 million families in the US and they build for 50,000???
Is that number at least 50,000 pages / second? (Which would be reasonable.)
- smartician 13y agoI think 50,000 concurrent users is actually a fairly reasonable number, given that not all US households are in the market for health insurance on the exchange, and that not everyone will be using the site at the same time.
- ars 13y agoYes, 50,000 pages per second is quite reasonable. But I suspect that's not what the number means here.
- deleted 13y ago[deleted]
- warfangle 13y agoConcurrent, perhaps. But a thing like this? You're going to see spikes of many, many times more than that opening [insert time period]. See also: the Slashdot Effect, the Digg Effect, et cetera.
- dangrossman 13y agoEven if they could theoretically make a site that can handle every person in the country using it at exactly the same time, it'd still be bottlenecked by the much older systems it relies on at the IRS, SS, VA, DOD, DHS, etc. As the article alluded to, the Healthcare.gov site checks your family size, AGI, social security benefit status, citizenship status, incarceration status, veteran status and enrollment in other government health programs during the signup process to determine what you're eligible for.
- cantankerous 13y agoThis. The article sorta pines in the end for smaller "more agile devs", but I'm not sure a small shop could just come in and bust this out. There is SO MANY legacy systems that need to interface with this beast. I wouldn't put it past the designers to have been rate-limited at 50,000 whatevers by one of the vendors of the other systems that they have to talk to. Computers from the IRS have been hanging in there sometimes as far back as 40 years ago. I'm sure systems at many other of the lettered agencies are hobbling along just as well. I totally agree that the government needs to become more lucrative to smaller more agile groups. I think it could ultimately get better products at lower prices if it opens up bidding. That said, the government has massive needs and massive legacy systems that many small shops may have a hard time reconciling. There's always ways to theorize about how the government could standardize and modernize its disparate stuff, but that requires strong leadership, a good direction, and money. None of these things appear to be in abundance right now. It's really unfortunate.
- justinsb 13y agoI posted this in another comment, but do you have any ideas as to why that information has to be verified in real time?
- dangrossman 13y agoBecause it can be, and doing so provides a better experience. If you have the chance to design a system from scratch, you're going to want the best design you can afford, right? So why not create a marketplace where buying health coverage is as simple and straightforward as buying speakers on Amazon -- a list of products with prices and a buy button. The asynchronous alternative is a menu of plans you may or may not qualify for, at prices that may change after you apply, based on inputs many people will get wrong (unintentionally and otherwise), with a true cost that won't be known until someone does your taxes up to a year later and computes what subsidies you qualified for. Even if there's only a day between signing up and verifying your information, that turns an hour of "getting it done and over with" into a multi-day ordeal. Considering this is a mandated purchase for a lot of people, they want to devote multiple days to it about as much as they want to stand in a long line at their local DMV.
- InclinedPlane 13y agoCompare this with the medicaid "part D" government website launched in 2006. It was designed around an anticipated load of 20,000 simultaneous users so they scaled it to be able to serve 150k users. Anyone who builds websites in 2013 without understanding the spiky nature of traffic or the necessity to build in capacity overhead is incompetent, end of story. The amount of money spent on building healthcare.gov (many millions) just makes that incompetence even more infuriating.
- dangrossman 13y agoBeing handed impossible constraints (serve 250k simultaneous users, verify them all with the IRS, but the IRS service you have to talk to can only handle 1000 simultaneous requests) isn't incompetence on the developer's part, and we don't know whether something like that isn't what's happening. The team that built this site (which has had no unintentional downtime, latency or server errors -- whatever code they wrote hasn't fallen over, it's just stranded most people on a "please wait" page when they try to register) has no power over systems at all the other agencies they have to work with.
- InclinedPlane 13y agoImpossible? That's just a constraint. If you have a dependency on some other service that is highly rate limited then you work around that, using any one of a kajillion different techniques. You don't just drop everything on the floor, throw up your hands and blame everyone else.