Trenching the Yard Like a Data Center: East/West Water Feeds, 220V Corner Drops, and Biological Firewalls
What happens when an infrastructure engineer plans a garden upgrade in Japan—treating spigots like availability zones, over-provisioning 220V corner power for Christmas lights, lecturing garden valves about Zigbee physics, and replacing weeding toil with groundcover.
When you spend your career designing distributed systems and homelab networks, it is physically impossible to turn that part of your brain off when you step outside with a shovel. Normal homeowners look at a backyard and see grass, bushes, and maybe a nice spot for a barbecue. I look at my yard and see single points of failure, unshielded runs, and an unacceptable amount of manual operational toil.
With autumn settling in here in Japan—bringing crisp air, clear skies, and a sun that won’t immediately give me heatstroke—I’ve been spending more time outside planning a proper overhaul of the garden. What started as a completely innocent question (“How do I stop dragging a 30-meter kinked garden hose around every corner of the house like a medieval peasant?”) rapidly escalated into a full-blown Layer 1 architecture review: multi-region water routing, triple-voltage corner power distribution, wireless protocol trade-offs, and biological firewalling.
Looking at the yard while mentally mapping out pipe and conduit paths gave me an immediate flashback to my OVHcloud days. Whenever I visited the data centers, all the surrounding access roads were covered in a rainbow of spray-painted utility markings—red, yellow, blue, and orange lines crisscrossing the asphalt everywhere existing power, cooling water, and fiber runs were buried, while civil crews continuously tried to cram even more conduits into the ground without hitting the old ones.
Here is how a simple weekend gardening project turned into that exact same data center floorplan—minus the asphalt, plus a lot of gravel.
Layer 1: garden-east-1, garden-west-1, and Trenching Under Gravel
In software, a bad database schema hurts, but you can always write a migration script, run it in a maintenance window, and pretend it never happened. In the yard, a “schema migration” is exponentially worse—especially because we already covered the ground in landscape fabric and gravel. Digging a new trench now means carefully raking back the gravel so it doesn’t mix with the dirt, folding back the weed barrier, excavating the trench, and putting the whole layer cake back together without making a mess.
Fortunately, Past Me had a rare moment of foresight when the house perimeter was set up, leaving the property pre-provisioned like a colocation cage:
- Dual East & West Water Availability Zones: Instead of a single outdoor spigot forcing one comically long pipe run all the way around the property (with the water pressure of a tired sigh by the time it reaches the far end), exterior water feeds sit on both the East and West sides of the house (
garden-east-1andgarden-west-1, naturally):- The West water supply feeds the West and South fence lines for drip tubing and local hose hookups.
- The East water supply feeds the East fence line, and will eventually branch up to the North side—which already has three conduits waiting in the ground like dark fiber, just no water line pulled through yet.
- Four-Corner
110V / 110V / 220VPower Drops & North Conduits: Every single corner of the house already has a triple exterior power drop (110V / 110V / 220V— two110Voutlets plus a220Vfeed) installed specifically for future yard shenanigans, plus those three pre-installed conduits on the North side. Do I currently need220Vof industrial juice at all four corners of my garden? No. Could I theoretically weld a tractor or run a 240V server rack in the hydrangeas if the mood struck? Absolutely. While the final garden endpoints for the remaining electrical runs are still undecided, tossing buried conduit into the trenches while they are already open for the water lines is a no-brainer—especially for powering Christmas lights and winter decor along the fence without turning the lawn into an obstacle course of orange extension cords.
Rule #1 of trenching is identical to Rule #1 of civil telecom engineering: the expensive part isn’t the pipe; it’s the hole. Digging the trenches once so the East and West water lines and buried electrical conduit share the same path means zero visible hoses and zero trip hazards for the next decade.
The Control Plane: Replacing Fragile Gardena Timers with LinkTap & Zigbee
Once water reaches the fence lines, someone still has to turn the valves on and off. Left to human memory, garden watering follows a predictable bimodal distribution: either the plants are parched for nine days straight, or someone leaves a tap cracked open right before a typhoon.
We originally went with Gardena for automated watering, assuming the big heritage brand name meant rock-solid hardware. In practice, the Gardena automation setup hasn’t lived up to its reputation at all—the timers and plastic valve assemblies turned out to be surprisingly fragile outdoors. (To give credit where it’s due, Gardena is still great for basic hoses and quick-connect fittings—just don’t trust their electronics to run your control plane.)
That sent me looking for a proper replacement, which is how I landed on LinkTap. What immediately sold me on LinkTap is that their engineers clearly understand radio physics and outdoor failure modes.
Half the “smart garden” gadgets on Amazon try to cram a chatty 2.4 GHz Wi-FiWi-FiIEEE 802.11 Wireless NetworkingNetworkingA family of wireless local area network (WLAN) radio protocols based on the IEEE 802.11 standards operating in the 2.4 GHz, 5 GHz, and 6 GHz spectrum bands. radio directly inside a plastic water valve sitting two inches off the wet dirt on the far side of a concrete-and-stucco exterior wall. Anyone who has ever debugged Wi-Fi knows how this movie ends:
- Wet leaves and exterior walls eat 2.4 GHz signals for breakfast, so the valve spends its life reconnect-looping at
-89 dBm. - Maintaining a constant TCP/IPTCP/IPInternet Protocol Suite (TCP/IP)NetworkingThe foundational four-layer suite of communication protocols (Link, Internet, Transport, Application) that powers end-to-end packet routing and transport across the global Internet. and Wi-Fi handshake chews through AA batteries faster than a 1990s Game Gear.
LinkTap takes the sane systems-engineering approach: a tiny wired gateway plugs into your indoor switch and talks to the outdoor valves on the East and West sides over a long-range, low-power Zigbee mesh protocol:
- Actual Wall Penetration: Lower-frequency, low-data-rate mesh packets punch through exterior walls and reach all the way out to the fence lines where standard Wi-Fi gives up the ghost.
- Two-Year Battery Life: Because a water valve only needs to exchange a few bytes of state (“open valve”, “still flowing”, “closed”), a pair of AA lithium batteries lasts up to two years.
- Hardware Circuit Breakers & Telemetry: If a drip tube pops off, a neighborhood cat chews through a line, or a valve fails to close, the built-in flow meter detects the abnormal flow rate, shuts the valve off, and pushes an alert. It is basically Prometheus alerting and automated circuit-breaking for dirt.
Eliminating Manual Toil: Port-Binding the Rock Wall
Google’s SRESRESite Reliability EngineeringReliabilityAn engineering discipline applying software engineering practices to infrastructure and operations problems to build ultra-scalable, self-healing distributed systems. handbook defines toil as work that is manual, repetitive, automatable, devoid of enduring value, and scales linearly as a service grows. Whoever wrote that chapter clearly owned a dry-stacked rock retaining wall.
Because our rock wall is built from stacked stone without mortar, the crevices between the rocks form hundreds of tiny, sheltered pockets of soil and moisture. To a weed seed, those crevices are free real estate. Pulling them by hand is the ultimate Sisyphean cron job: you spend two hours clearing the wall on Saturday, it rains on Tuesday, and by the following weekend a brand-new generation of weeds has spun up in the exact same cracks.
Since apt remove --purge weeds isn’t available in real life, the fix is biological resource saturation: intentionally packing low-growing flowers, compact shrubs, and creeping groundcover directly into every joint of the rock wall. Right now I’m leaning toward planting Delosperma (ice plant)—it’s tough, loves wedging itself into sunny rock crevices, and carpets the stone in bright, pretty flowers. If Delosperma and creeping groundcover already occupy 100% of the root space and shade out the gaps, airborne weed seeds have no soil to land on and no sunlight to germinate.
In systems terms: if you don’t want rogue processes binding to an open port, bind your own daemon to it first.
Perimeter Firewall Policy: Pyracantha (DROP) vs. Star Jasmine (ACCEPT)
The final architectural debate is what to plant along the perimeter fences.
Initially, my inner security engineer looked at pyracantha (firethorn). From a pure perimeter-defense standpoint, pyracantha is a Cisco ASA in shrub form: dense, evergreen, covered in bright berries in autumn, and armed with needle-sharp thorns that will impale anything—human, animal, or stray soccer ball—that attempts unauthorized ingress.
The catch is the operational maintenance cost. A bush armed with two-inch thorns does not distinguish between a burglar and the guy paying the mortgage. Anything that is medieval torture for an intruder to climb through is equally medieval when you are the one who has to prune it twice a year, sweep up spiky trimmings where your kid plays, and smell its blossoms in the spring—which, by some cruel joke of botany, smell vaguely like a forgotten gym bag.
After weighing perimeter defense against day-to-day quality of life, I’m dropping the thorny firewall and going with star jasmine (Trachelospermum jasminoides / テイカカズラ) and similar aromatic climbers instead:
- Evergreen coverage across the fence year-round
- No thorns to stab you every time you trim the fence
- A warm, sweet floral scent across the yard when the weather warms up
Sometimes the best architecture isn’t the most locked-down fortress—it’s the system that won’t draw blood when you do routine maintenance. Now comes the real physical toil: peeling back all that gravel and landscape fabric to get the trenches dug once and for all—which will almost certainly be outsourced, because every good architect knows when to delegate Layer 1 excavation to a managed service provider.

About the author
Ed Stuurman
Infrastructure and reliability engineer based in Japan. Passionate about resilient systems, bare-metal hardware, cloud automation with Terraform, and all things homelab.
Contact
Thoughts or questions on this article?
Found a bug, tested a similar setup, or want to discuss the details? Drop a message below.