The jungle is getting denser — and that’s a good thing.
🧠 What Is Jungle Computing?
When researchers from the University of Amsterdam and VU Amsterdam first coined the term Jungle Computing back in 2011, they used it to describe something that was already happening quietly in scientific computing — the growing mix of clusters, grids, clouds, GPUs, and local machines all being used together in one tangled, interdependent ecosystem.
They compared it to a jungle because of its diversity and complexity:
each computing “species” — whether it’s a cloud instance, GPU cluster, workstation, or IoT device — coexists and contributes to a larger, distributed habitat.
At its core, Jungle Computing means leveraging heterogeneity.
Instead of trying to unify everything under one cloud or one platform, it accepts the mess — and then turns it into an advantage.
It’s the recognition that compute now happens everywhere — from data centres and edge devices to browsers and mobile chips — and that the challenge (and opportunity) is to orchestrate this diversity intelligently.
🌐 Why It Matters Now
Fast forward to 2025, and Jungle Computing isn’t just a research idea anymore.
It’s quietly become the default architecture of the modern internet — even if we don’t call it that.
- Hybrid workloads now span local edge, cloud, and client compute.
- PWAs, WebAssembly (WASM), and WebRTC have turned browsers into active compute nodes.
- AI inference runs locally on devices while heavier tasks sync back to cloud or distributed peers.
- Scientific clusters and commercial platforms alike now juggle CPUs, GPUs, and TPUs without distinction.
We’re living in a Jungle Computing era — where the diversity of compute is the system.
It’s no longer just “distributed computing” — it’s heterogeneous computing by design.
🏗️ How It Works
In Jungle Computing, every compute node — whether a supercomputer, Raspberry Pi, or browser tab — becomes part of a shared network.
The orchestration layer decides what runs where, based on cost, capability, latency, or availability.
Typical features include:
- Heterogeneous resource pools (CPUs, GPUs, edge, browser, mobile).
- Dynamic resource discovery (nodes can join or leave freely).
- Lightweight coordination servers (not monolithic control planes).
- Encrypted and signed compute events (DLT-backed audit trails).
- Local-first execution (minimise round trips; sync later).
It’s not about pushing everything to the cloud — it’s about letting every layer contribute according to its strengths.
🧩 Real-World Examples
- Scientific Simulations – Multi-model climate or astrophysics simulations that link clusters, clouds, and GPU nodes across institutions (e.g. Drost et al., 2012).
- Edge AI Networks – Cameras, vehicles, and IoT sensors performing inference locally, then syncing global models periodically.
- Enterprise PWAs – Modern web apps (like your EPC concept) using browser-based compute and local caching, syncing to central servers only when required.
- Distributed DBs – Systems like Gun.js, CouchDB, and IPFS that replicate data across devices — partial, local copies forming a living ecosystem.
All of these are Jungle Computing in practice — diverse nodes contributing to a shared goal.
🧰 Open-Source Foundations
For anyone exploring Jungle Computing today, the open-source landscape is already rich with tools that can form its backbone:
| Library | Description |
|---|---|
| wasm-peers | Rust → WASM wrapper for WebRTC DataChannels — enables browser-based peer compute. |
| Gun.js | Decentralised graph DB (CRDT-based) for sync between browser peers. |
| Rings Network | Structured P2P overlay network supporting WebRTC + WASM; built for distributed coordination. |
| Veilid | Rust-based P2P application framework for encrypted peer discovery and communication. |
| sqlite-wasm-webrtc | Local SQLite DB in-browser with WebRTC replication — proof of concept for browser-node sync. |
| Matchbox Socket | Peer-to-peer socket layer for WebAssembly and browser multiplayer workloads. |
| GNUnet | Privacy-preserving P2P framework — foundational for secure distributed systems. |
Together, these form a toolkit for modern Jungle Computing — small, modular, open, and browser-ready.
They allow any device with a browser to join the “jungle” as a contributing node — the ultimate heterogeneous environment.
🧩 The Challenge Ahead
As with any complex ecosystem, the challenge is balance.
How do you maintain order in a system built for diversity?
How do you discover and coordinate resources without over-centralising?
This is where Jungle Computing research continues to evolve — in resource discovery (HARD, RDAD), intelligent scheduling, and hybrid orchestration models that can scale across local and global domains.
Expect to see this space accelerate fast in 2025 and beyond — especially as AI workloads push further to the edge, and browsers continue to mature as runtime environments for distributed apps.
🌴 A Glimpse Toward “Island Computing”
While the jungle thrives on interconnection, not every node stays online.
Sometimes, clusters or browsers go offline — becoming small autonomous systems that continue working, storing, and evolving locally.
These disconnected nodes act like islands in the wider jungle.
They live independently but rejoin the network periodically to sync data or trade computation.
That idea — Island Computing — is something I’ll explore next:
What happens when each island has its own ecosystem, but together, they form a living, global network?
Stay tuned.
– Andrew Bartlett
Developer, systems designer, and curious observer of the digital jungle.
Jungle Computing Simulator

