… its a website run by the US Government. Why does it have such large downtimes in this day and age?

  • @really@lemmy.world
    link
    fedilink
    English
    431 year ago

    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.

    • krolden
      link
      fedilink
      English
      51 year ago

      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.

      • @turmacar@lemmy.world
        link
        fedilink
        English
        9
        edit-2
        1 year ago

        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”.

      • @ngdev@lemmy.world
        link
        fedilink
        English
        31 year ago

        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

          • @ngdev@lemmy.world
            link
            fedilink
            English
            11 year ago

            lol i was more or less just remarking on the fact that yes mainframe and other legacy apps are pretty old, however that does not mean that they’re necessarily worse than a modern implementation