In the War Room, the air uncoiled like a violin string finally releasing its tension. There were no explosions. No red alarms. Project Aegis had been deployed to production.
"Deployment successful," Kael announced. His voice sounded firm, professional, rehearsed. But a treacherous drop of sweat slid down his perfectly shaved temple. "The validation walls are active. The perimeter is secure."
Vincent leaned over the holographic table like a vulture over prey. "Status of the WaterFactory?"
Kael typed a quick query into his titanium terminal. "Stable. Zero exceptions. Zero NullPointers. The system is rejecting any malformed requests before they touch the core. It's... perfect."
Vincent smiled, a predatory smirk that showed too many whitened teeth. "Excellent. I'll draft the report for the Board immediately. 'Critical incident resolved via high-level standard security protocols.' Robert, make sure this goes into Kael's quarterly review. I want this kid promoted to Senior before the end of the year."
Robert, however, wasn't looking at the error counter. He was looking at the Response Time graph.
Before the patch, the line hovered at an agile 200 milliseconds. Now, after the deployment of the walls, the baseline had jumped to 350 ms.
"We've lost velocity," the Architect muttered, frowning.
"That's the expected overhead penalty for security, sir," Kael rushed to say, snapping his laptop shut with a decisive click. He had read it in the textbooks: security costs CPU cycles. "A 75% increase in latency is acceptable within ISO operating margins. No one is going to notice an extra tenth of a second."
Robert nodded slowly, wanting to believe him. He desperately wanted the bug to be squashed so he could sleep for more than four hours. But in the back of his brain, the workshop technician's voice echoed like a nagging background process: Don't try to push the cars when they stop.
Six hours later.
Kael was alone in his 42nd-floor office, a glass cubicle overlooking the polluted city. He loosened his Italian silk tie and stared at his reflection in the tinted window.
He didn't see Macro-Systems' "Star Engineer." He saw an eight-year-old boy crying in front of a screen full of C++ code.
"The code does not forgive, Kael," his father, the Grand Architect of Omni-Corp, had told him after Kael forgot to free a pointer in his school assignment. "If you leave the door open, chaos enters. And our family does not tolerate chaos. We are Soli. We are the Structure. If you fail, the family name fails."
Kael shook his head, clearing the ghost of his father from his cache. He had delivered. He had built a flawless fortress around the bug. He had followed the rules.
He glanced at his secondary monitor. Current latency: 600 ms.
The number was flashing yellow. It had spiked. Kael felt a knot in his stomach. It was probably just the afternoon rush hour traffic. The walls were doing their job, asserting every request one by one. It was normal for it to spike a bit. The system was robust. It had forty layers of logical concrete. Nothing could break it.
"It's secure," he told himself, like a mantra. "Slowness is the price of perfection."
He tried to ignore the integer. But the number kept incrementing, slow and inexorable, like water rising in a sinking ship.
In the basement of the building, in the gray, windowless cubicle of Level 1 Support, hell was beginning to freeze over.
Molen had his headset on, but he wasn't listening to Lofi beats. He was listening to human frustration streaming in real-time.
"Macro-Systems Support, Molen speaking."
The author's content has been appropriated; report any instances of this story on Amazon.
"Hey! The system isn't loading. I've been staring at a 'loading' spinner for a minute. What's going on with my order?"
"Understood. Did you get any error messages on the screen?"
"No, no error. It just... hangs there thinking. The wheel keeps spinning and spinning. Did the server crash?"
Molen checked his own diagnostic monitor. All the lights were glowing bright green. According to the official dashboard designed by the Soli, the system was "Healthy." There were no red errors.
But Molen knew exactly what was happening. There were no errors because the errors were trapped in the queue. The system wasn't dead; it was catatonic.
"Sir, the system is operational, but we are experiencing... high congestion," Molen lied, parsing the official script Vincent had blasted over email. "Please do not refresh the page. If you refresh, you will lose your spot in the validation queue."
He disconnected. Immediately, another call dropped in. And another. The support ticket dashboard, which usually maintained a steady throughput of 10 tickets per hour, now showed 300 tickets pending in the queue.
They all reported the same bug: "Sluggish," "Frozen screen," "The system is ignoring me."
Molen closed his eyes for a second. He visualized the highway he had mapped out earlier. Kael's guards were stopping every single car. At first, with low traffic, it worked. But now, at 3:00 PM, thousands of users were trying to hit the ERP. Every user generated a request. Every request was halted roughly 40 times by Kael's walls. The payloads started to pile up. The RAM wasn't filling up with data; it was maxing out with execution threads just waiting in line.
The server wasn't processing. It was holding its breath.
Molen felt a bitter helplessness. He had the patch compiled in his head (the Box, the Optional), but he was trapped on the phone, apologizing for a catastrophic failure he had predicted using traffic metaphors.
It's a lead armor, Molen thought. Kael strapped a marathon runner in lead armor so he wouldn't get shot. Now he's not going to die from a bullet... he's going to die of exhaustion.
War Room. 04:45 PM.
The triumphant silence of the morning was completely wiped. Now, the atmosphere smelled of electrical panic and burnt ozone.
Robert was standing in front of the massive screen. The latency graph was no longer an ascending curve. It was a vertical wall. Current latency: 15,000 ms (15 seconds).
"Kael!" Robert roared, throwing his composure out the window. "What is going on?! The system is practically halted!"
Kael was typing frantically on his laptop, pale as a ghost. His pristine hands were shaking. "I... I don't understand. There are no errors. There are no NPEs! The walls are working. The code is secure. The logs are clean!"
"The code is so secure that no one can use it!" Robert yelled. "Look at the Thread Pool queue! It's at 99% capacity! They're all blocked waiting for validation!"
At that exact moment, the screen flickered. The "Healthy" green color vanished. A new alert flooded the room. It wasn't the violent, sharp red of a NullPointerException. It was a sickly, suffocating orange.
The orange of a Timeout.
java.util.concurrent.TimeoutException
Request timed out after 30 000 ms
"It's over," Robert whispered, collapsing into his chair.
"It's just a timeout," Kael said, his voice cracking, clinging to his denial like a castaway to driftwood. "It's... it's the network. It must be the ISP. My walls don't cause this. The logic is flawless!"
Vincent burst into the room, his face contorted, a phone glued to his ear. "The Board of Directors is on the line!" he roared. "They're saying financial transactions have stalled! We are losing millions a minute! Kael, you swore on your degree that this was impenetrable!"
"It is!" Kael shouted, on the verge of tears, looking at his boss with the eyes of a terrified child. "The bug can't get in!"
"Neither can the money, you idiot!" Vincent bellowed, hurling a folder across the table.
Robert surveyed the chaos. He looked at Kael, paralyzed because reality didn't compile with his textbook. Kael wasn't a villain; he was a straight-A student who had never deployed to the real world. He looked at Vincent, frantically searching for a scapegoat to salvage his annual bonus.
And then he looked at the blocked threads graph. Thousands of cars parked on the highway, engines running, burning gas until they died.
The system hadn't crashed. The system had suffocated under its own weight.
Robert remembered the voice of the kid from the workshop. The JIT. "It will time out waiting. It's going to be a swamp."
The Architect made a decision. If he was going down, he wasn't going to do it following a manual that had just flatlined his system. He needed instinct. He needed someone who could listen to the rhythm, not just read the documentation.
"Vincent," Robert said, with a terrifying calm. "I need Root Level clearance."
"For what?" Vincent spat. "To deploy more walls?"
"No. To bring in someone who knows how to blow up the dam."
Robert pulled out his personal phone and pulled up a number he had queried from the HR database that very morning—"just in case."
"Kael, get out of my chair," Robert ordered. "I'm calling tech support."
> Enjoyed the code? If you want to buy this Dev an energy drink (BMAC)
or read upcoming chapters early (Patreon), check the links:
https://buymeacoffee.com/molaya
?? Patreon:
Also you can read it in my web page:
__________________________________________________________________