![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Oh gods, this is a mess. Setting aside the fact that I slipped on a morning update and created a few hundred classes accidentally, which we are unable to delete (yes, I'm not perfect—just damned lucky my boss is nice), other things are going on which make me sort of want to hide under my desk and whimper.
This is all work stuff, so sorry if it's boring as all hell. Right now we have three things wrong with our system. 1: Not enough diskspace. We need at least twice of what we have just to continue limping forward into the bright new dawn. This has already caused us innumerable problems in the way of database corruption. 2: Only two servers. This may not sound horrible, but one is an application and one is a SQL. 3: A forthcoming upgrade of the application.
Now, problems one and two are fairly simple to take care of. We have new servers, including a load balancing system that cost a small fortune but dear gods do we need it. \o/ A clean transfer of the database to those servers will get us cheerfully up and running at full speed. It starts getting messy when the upgrade is considered. We're not ready to upgrade yet. And the best way to upgrade is to simply start with the new system. Upgrading over a current system is part of the reason we're in trouble now. But we won't be ready for about a year—so what do we do? Install the old system and let it run for a year, creating a year's worth of mess that we'll have to figure out how to handle later? Or continue oozing along and praying nothing breaks irreparably?
I say this like I have any say in the matter. Thankfully, I don't. Never before have I been so glad to be a peon (though I'd like a bigger paycheck, plzkthx).
This is all work stuff, so sorry if it's boring as all hell. Right now we have three things wrong with our system. 1: Not enough diskspace. We need at least twice of what we have just to continue limping forward into the bright new dawn. This has already caused us innumerable problems in the way of database corruption. 2: Only two servers. This may not sound horrible, but one is an application and one is a SQL. 3: A forthcoming upgrade of the application.
Now, problems one and two are fairly simple to take care of. We have new servers, including a load balancing system that cost a small fortune but dear gods do we need it. \o/ A clean transfer of the database to those servers will get us cheerfully up and running at full speed. It starts getting messy when the upgrade is considered. We're not ready to upgrade yet. And the best way to upgrade is to simply start with the new system. Upgrading over a current system is part of the reason we're in trouble now. But we won't be ready for about a year—so what do we do? Install the old system and let it run for a year, creating a year's worth of mess that we'll have to figure out how to handle later? Or continue oozing along and praying nothing breaks irreparably?
I say this like I have any say in the matter. Thankfully, I don't. Never before have I been so glad to be a peon (though I'd like a bigger paycheck, plzkthx).
