… its a website run by the US Government. Why does it have such large downtimes in this day and age?
We know why but pointing out how Republicans only policy position is “explicitly kneecap everything so we can privatize it and funnel money to our friends at non negotiated rates 5x the normal end user retail cost” is apparently not allowed because some guys like guys and some people want to alter a pronoun by one letter or some such shit.
at this point i don’t even think its that deep anymore sometimes. Sure they do things like that. But at this point…sometimes they really are just fucking cartoon villains. Being evil just because.
That’s how I feel gesturing broadly at the 3 or 4 states they’re still actively fighting against minimum marriage age laws.
Their voters out here voting for them to “protect children” from pronouns, from books, from learning - then turn a blind eye when they vote to make marrying at 12 legal again or to force 12 year olds to give birth or to send 12 year olds back to the mines. Not only are the politicians cartoon villains, in 2023 so are their voters. Full Stop.
I’m going to have a guess and suggest that the website is probably integrated with some much older mainframe system and a batch process or several batch processes run daily overnight to shuttle data between the two systems to keep them updated and in sync.
Syncing the two sets of data while the database is live and changing is a pain the the bum, so they freeze it while the data transfers are taking place.
This is the real answer. Main frame batch processing.
And till you haven’t experienced it, it seems like an excuse. Why can’t you simply do it all the time. Why can’t you get rid of the mainframe, etc.
But if only it were that easy. There is a reason IBM can still acquire multi billion dollar companies and then run them into the ground.
My company has maybe a couple million customers and can’t get rid of its mainframe and in areas that it’s gotten the process away from the mainframe, batch patronizing is still a thing. Because that is the only way to guarantee integrity.
So yea. I wish your comment gets more up votes. Because it is not a conspiracy, it is a technical limitation.
I like working with legacy systems. Post something, go fart around on your phone for fifteen minutes while you wait for it to post.
I had to do some legacy app modernization for one of the largest telecoms companies in the US, and their mainframe system and the UI, while ugly, performed so much faster than the modern approach.
Given, we weren’t the most talented team out there, but rendering the UI on the server side was unmatched in performance versus what we could get out of a web browser. I was the UI guy so I didn’t really touch mainframe side, but it was wild to me that they made this system like 30 years ago and it worked so much better than our modern implementation
Its the conspiracy of capitalism. If nothing else this is another example of how megacorps have more say in government operations that the entire population.
It can be, but it’s also an issue of “move fast and break things” doesn’t work in all environments.
You don’t want your bank to have an oops with your checking account, or your medical records to get messed up because someone didn’t code it well enough. If it works and is stable, there needs to be a demonstrable benefit and a guarantee that it will keep working when moving to a newer system. Usually on a budget of “what do you mean you need a budget, just do it”.
This also explains, very basically, why financial systems are the way they are. The backend is ancient but they know how it works so it stays the same and we see it’s weird quirks all the time.
More like, they know of they try to change, and their is an issue and people’s statements payments are at risk, it’s their ass.
I particularly enjoy the “if you need immediate assistance” note for a telephone line that’s open even fewer hours than the website. it’s positioned as an alternative to the site, but absolutely isn’t. Also, if that message is only displayed when the site is closed, there are no hours when the phone line is open but the site is closed, so who’s it helping? You couldwrite it down and call it when it’s open, but the site is also going to be open then, several hours earlier in fact, so is less “immediate” than the site that’s closed.
Well damn, that web server has a good union.
The hours unavailable:
| Day | Time Offline | Start | Stop |
|---|---|---|---|
| Monday - Friday | 4 hours | 1am | 5am |
| Saturday | 6 hours | 11pm | 5am |
| Sunday | 8½ hours | 11:30pm | 8am |
| Total | 34½ hours/week |
The first one sounds like “scheduled maintenance” gone awry. Like for something that takes 5 minutes to run that you tell your boss will take an hour, who tells his boss it’ll take two hours, boss then says “let’s double that to be safe”.
I wanna know WHY it is unavailable. Does the system crash if there’s not enough paper in the dot-matrix printer? Are the HTTP responses being filled out manually in real time?
We have the same for the tax system in Sweden. The reason there is multi part but two big ones are:
Guarantees around how long time processing your tax information will take. But this gets harder if your information comes in at off hours since the tax information still needs a human stamp of approval (which really is making sure the system didn’t flag it as manual review which happens at random and if there are discrepancies)
The second, related one, is that they do batch processing at night and while they could queue data for the next day doing so would require a rewrite of the law guaranteeing a certain processing time, since if your data comes in after the start of the batch run it won’t run until the next day, which would be hard to properly inform people about in a way they’ll accept. Better then to simply not accept it then.
It’s like saying “This law ensures your application will be processed in 48hrs” then everyone rejoice and vote! But instead of adding more manpower to process they limit the application coming in. Sneaky.
While I get your point I don’t really agree. This law/requirement on the tax agency predates digital tax forms and is the same if you send in on paper. It’s more about how they don’t want to make things more complicated by having different rules for different media. It’s still so much more simple to use the digital forms / system and very few people actually need these systems online during the night and even fewer companies. The benefit is simply far outweighed by the cost. Remember it would be tax payers that have to pay for the system being available 24/7 with everything that entails in increased support costs and infrastructure costs due to the higher SLA levels required from all parties involved.
