An Act of Revolution

The underground lights in the Resistance Headquarters flickered as the generators switched circuits. Omari sat cross-legged on the cold tile floor, a tablet balanced on his knee, wires snaking from it like ivy. Across from him, Zia hovered beside a dusty folding table, watching charts ripple across her screen.

“Multilada’s fast,” she said, almost to herself. “But the data layer feels… sluggish.”

Omari nodded. “Yeah. We need to talk about ADAIL Relational Databases—ARD.”

Zia pulled up a visual of Multilada’s backend on her tablet. “I thought we already had a database spun up?”

“We do. One instance. But that’s like having a single librarian in a city-wide library. You want Multilada to scale, right? Then we need to give it a proper architecture.”

He tapped a few commands into his tablet, and a 3D schema projected above them, ghostly blue against the concrete walls. In the center, a single glowing node pulsed—Primary Instance.

“This is your source of truth,” Omari explained. “The primary database instance. It handles all writes—new user data, course completions, knowledge points gained.”

Zia squinted. “But if everyone’s hitting that one instance…”

“It’ll choke,” Omari finished. “That’s where replicas come in.” He swiped his fingers, and three additional nodes blinked into view, orbiting the primary like satellites. “Read replicas. These handle read-only requests—anything that doesn’t change the data. Course queries, lesson lookups, dashboard loads.”

“Distributed reading,” Zia said. “So it doesn’t bottleneck.”

Omari grinned. “Exactly. You split the load. Plus, if the primary ever fails, we can promote a replica to take over—minimal downtime.”

Zia leaned closer, curious. “What about backups? What if something corrupts the data?”

Omari tapped again. A line emerged from the primary node, ending in a storage vault marked Snapshot-073. “Automated backups. ADAIL runs them daily, but we can trigger snapshots anytime—full images of the database, stored securely in ADAIL Object Storage.”

“Like checkpoints in a game,” Zia said, starting to smile. “You screw up, you roll back.”

“Exactly. And we can even encrypt the snapshots with AKM—ADAIL Key Management—so if the Purists ever get their hands on them…”

“…they get noise,” she finished.

Omari’s eyes narrowed as a console beeped. “We’ll also enable Multi-AZ deployment. That means ADAIL will automatically provision a standby instance in another availability zone—like a second data center. If the primary zone goes dark, failover kicks in.”

“Resilience,” Zia murmured. “Every part of this system is built to survive.”

He gave a quiet nod. “That’s the goal. We’re not just storing test scores and course completions. We’re protecting intellectual ammunition. Multilada is going to carry the knowledge of a generation. And ARD… that’s where its memories live.”

Zia sat in silence for a moment, taking it all in. Then, softly: “You’ve built cities in the clouds, haven’t you?”

Omari laughed. “More like underground tunnels through the clouds. But yeah. And I’ve learned something important: databases aren’t just storage. They’re strategy. A well-placed replica, a timely snapshot—that’s what keeps a rebellion from being erased.”

A crackling voice echoed from down the hall—Kai’s, summoning them to the ops room.

Omari stood, extending a hand. “Come on. Let’s make Multilada not just smart, but unkillable.”

Zia took his hand and rose, the plan already forming in her mind.

As they walked off, the 3D schema still floated above the table—nodes pulsing gently, quietly promising persistence in a world built on forgetting.