Cloud infrastructure

RESILIENCE / STORAGE & OBSERVABILITY

Recovery is part of the design.

I treat backups, recovery planning, and monitoring as connected parts of managing infrastructure. A storage system protects data; an observable system helps explain what happened.

01 / BACKUP

Protect the working state.

My local environment includes a Synology DS1618+ for storage and backup work. The 3-2-1 backup strategy is a useful design baseline: keep three copies of important data, on two types of storage, with one copy off-site. Infrastructure definitions and application data need different handling: one describes how to rebuild a system, while the other preserves the state it depends on.

02 / RECOVERY

Plan the return to service.

My cloud-service work at Hong Kong Telecom included recovery planning and execution. That experience informs how I approach dependencies, restore procedures, and the order in which systems should return.

03 / MONITORING

Keep the system understandable.

I use Grafana for infrastructure monitoring. My Crypto.com work included L1 blockchain infrastructure monitoring, while my Pinax role includes monitoring and optimizing blockchain operations.

Connecting cloud and local infrastructure

My current infrastructure work brings together Terraform, container tooling, local storage, and Grafana. The project overviews connect those tools to the systems they support.

Explore the infrastructure projects