Overview

I always think it’s a great idea for every dead serious software developer to personally own a DIY data center, not from cloud provider BS, but a bare metal data center that you can see every solder joins from its mainboard, feel the weights of its CPUs, feel the difficulties of making components work together, etc. Those feelings will make you ascended to higher dimensions.

Joking aside, but it’s cool to:

• Experience how your applications get delivered from A to Z.
• Know in-depth how the infrastructures that support the applications actually work and get deployed.

Especially in these days, where this industry diverses into multiple jobs, roles and positions, most developers just code passively, merge PRs and wait for features appear to different development environments with bare minimum knowledge of how things work outside their application boundaries.

Then I plan to build a DIY data center.

Shopping spree

First, this is the hardwares after the long period of searching and dealing

The OS layer

After finish assembling hardware components, I install the proxmox and make this hypervisor type 1 server

This is how it’s look like

Data center health check (proxmox integrates with influxdb and grafana)

Data center architecture

For the gateway of the data center system, I choose pfsense , in short, it is a firewall / virtual router that help the data center to connect with outside internet.

As we can see in the architecture diagram, I split the system’s network into 2 separated zone: the standalone app zone and the shooting ground kubernetes cluster zone:

• The standalone app zone: this zone is for simple apps that help me everyday like pastebin, image hosting app, etc. I use docker compose installed on top of proxmox’s LXC container to run the apps (all are free docker opensource image).
• The Shooting ground k8s cluster zone: This is for me to gain knowledge and practice about kubernetes and enterprise delivery pipeline.

How I install k8s cluster

There are a lot of codies in the market talk about how useful k3s is and how it’s superior to minikube. But to me, both are non-serious toys, comparing them just like talk about how mature the 6-year-old kid is comparing to 5-year-old kid.

I use talos linux , first I download its iso and upload to proxmox. Then I create 4 VMs with talos linux iso and join them together into a cluster (1 master and 3 slaves)

• k8s master
• k8s slaves

This setup is the closest to the industry production-graded k8s cluster.

Conclusion

Building this DIY data center has been one of the most rewarding side projects I’ve ever worked on. From researching hardware compatibility, assembling every component, configuring the BIOS, installing a Type-1 hypervisor, designing network topology, deploying Kubernetes, and finally hosting my own applications, every step help me to broaden my horizons.

If you’re serious about understanding distributed systems, infrastructure, or cloud-native technologies, I’d recommend building a home lab at least once. It doesn’t need to be expensive, and it doesn’t need enterprise hardware. Start small, break things often, rebuild them, and gradually evolve your setup; you’ll gain something that’s difficult to obtain from tutorials alone: intuition.

And in software engineering, intuition is often what separates someone who merely uses technology from someone who truly understands it.