CyberChurch: Operational Spatial Utility Network

The Inspiration

As highlighted on the main stages of global spatial computing conferences like AWE USA 2026, the modern intersection of open XR infrastructure and decentralized learning environments represents the true digital frontier. Traditional mobile applications treat 3D environments as closed, isolated packages. We were inspired to challenge this paradigm.

CyberChurch was conceived as a highly scalable, interconnected network of 100 private spatial webpages disguised as tactical battlegrounds. Our mission was to merge compelling mobile tower defense gameplay with industrial-grade cloud performance, proving that complex data environments can be navigated seamlessly on standalone and mobile devices.

How We Built It

The front-end client layer is constructed within Meta Horizon as an array of 100 unlisted, interconnected spatial sectors. To orchestrate this massive environment without bottlenecking mobile compute cycles, we engineered a dedicated Operational Spatial Utility Network on Google Cloud Platform:

1. Serverless Ingestion Layer: 100 dedicated Google Cloud Run service instances act as spatial endpoints, receiving real-time player action metrics and vector paths using a dynamic scale-to-zero model to maximize budget efficiency.
2. Telemetry Management Matrix: Ingested coordinates flow securely via Direct VPC Egress into an enterprise High-Availability database cluster.
3. Optimized Spatial Logic: To process real-time containment rules and geofencing calculations instantly on mobile screens, we implemented a specialized 3-tier index structure, yielding a 50% optimization sweep across all deep spatial matching operations.

Challenges We Faced

Our primary hurdle was mitigating high-velocity telemetry data loops. In a fast-paced tower defense environment, concurrent entity tracking can easily trigger connection spikes and performance degradation on mobile processors.

To overcome this, we designed a resilient, self-healing system defense mechanism. We engineered a customized backend circuit-breaker framework named trg_self_heal_nodes. The moment a data loop or transaction overload threatens network stability, the circuit breaker instantly trips—terminating runaway backend processes, shedding connection bloat, and enforcing an exponential back-off routing protocol on the ingestion endpoints until the room stabilizes into a healthy state.

What We Learned

Through this intensive pre-production cycle, we proved that treating spatial design through the lens of traditional web paradigms—structuring virtual worlds as lightweight, link-accessible "spatial webpages"—radically simplifies asset distribution. More importantly, we learned that true system resilience isn't just about handling peak loads; it is about building automated, self-healing architectures that protect the user experience from cascading infrastructure bugs behind the scenes.

Built With

• direct-vpc-egress
• google-cloud
• google-cloud-run
• jsonb
• meta-horizon
• pl/pgsql
• postgresql-18-ha
• sql
• virtual-private-cloud-(vpc)