2 ms·
You're neglecting to consider an important difference between Twitter and Healthcare.gov, which is that they have completely different usage patterns. Even if w
by chatmasta 12y ago
You're neglecting to consider an important difference between Twitter and Healthcare.gov, which is that they have completely different usage patterns. Even if we assume Twitter and Healthcare.gov serve the same number of users, the engineering and scalability challenges of Twitter far outweigh those of Healthcare.gov. Active Twitter users engage with the platform daily, often simultaneously with millions of other users, and expect state changes to propagate across the platform immediately. Healthcare.gov, on the other hand, barely even has a concept of "active" users. For the most part, each user only engages with the website once at sign up, and then periodically thereafter. Users do not have an expectation of immediate propagation of state change. As long as the site works, nobody cares how long it takes for the accounting system to update.
My point is that you're comparing apples and oranges. Equating raw user numbers alone is not a fair comparison, because that's not what causes the engineering problems that make Twitter hard to scale. It's the usage patterns of those users that create the challenges.
Healthcare.gov is one step up from a static website, and customers rarely engage with it throughout their lifecycle. It's absurd to suggest that developing it should cost anywhere near the same as developing Twitter.
- colmmacc 12y ago> Even if we assume Twitter and Healthcare.gov serve the same number of users, the engineering and scalability challenges of Twitter far outweigh those of Healthcare.gov. I may have a bias because of my background, but I absolutely don't agree. Twitter is a very busy service, a planet-scale multi-way messaging bus isn't trivial by any means, but that part is still a relatively well defined, small in scope, engineering problem and something a small team of talented engineers could tackle. That's probably the easiest part to account for. Healthcare.gov on the other hand is gigantic in scope and faces many ill-defined problems; "integrate" with 50 states and various other administrations and insurance providers and so on to deal with, all of which are a moving target. In my experience the cost of having things poorly defined is something like 100x having something well-defined, and increasing scope is a lot more costly than increasing scale.
- chatmasta 12y agoAh, I understand your point better now. You're comparing scope vs. scale as an engineering bottleneck. That does make sense, simply because number of engineers need to increase linearly with scope, but not necessarily with scale. Put another way, scalability problems are a subset of scope problems. Still, I get the sense that the government threw way more money and engineers at this than necessary. The fact that a few relatively small "repair teams" could join the project after development and fix all the problems, makes me wonder if those problems really needed to exist in the first place. Perhaps it would have been better to group these 1000's of engineers into smaller groups of ~100, and have them compete with each other to implement specs in the fastest/best way. Pay each engineer a base salary, and then allocate the remaining money to a bonus system that incentivizes fast and quality development. All that said, I'm talking out of my ass. :)
- MaysonL 12y agoThere's also a major difference in rollout: Twitter scaled slowly, with quite a number of fail-whale episodes. Healthcare.gov rolled out to millions of users from day one, with everything necessary required to be there at the beginning.