And deploy it on what? The assumption here is the hardware can't handle the load. Deploying a new VM on the same hardware isn't going to make it faster.. quite the opposite. Virtualization doesn't solve all problems, especially when it's probably running on underpowered hardware.
Remember above when I said "Deploy another host?" That hardware.
Adobe has another zero-day for their document reader? We call this, "Tuesday."
Adobe has another zero-day? We call this "Tuesday."
Deploy another host, deploy another template VM to distribute load? Surely it's a plug-in, click/drag fix once they add a new host, right? +1 Scalability.
The website is extremely vague as to timelines of what system was in place when there were issues. Was
Does it run Linux?
Next thing you know, I'll have to pay royalties next time my damn blinker in my car matches the beat of a song on the radio.
One of the coolest [no pun intended] I did
I accidentally my own comment.
One of the coolest [no pun intended] *HACKS* I did
One of the coolest [no pun intended] I did was to place a hard-drive in the freezer overnight so that I could recover data from it the next morning. It took about 3 or 4 days to completely recover the data I needed to, but it definitely worked wonders.
As of next Tuesday, C will be flushed in favor of COBOL. Please update your programs.