CARLOS DAVID GONZALEZ VIVAS← BACK TO SELECTED WORK
SELECTED WORK / 04OPERATE

INFRASTRUCTURE · RELIABILITY · SECURITY

Keep it available.
Keep it resilient.
Know what happens.

A digital product also has to survive the real world: traffic changes, deployments, migrations, failures and malicious activity. I have built and operated cloud environments where availability, visibility and recovery matter.

My work spans architecture, deployment, monitoring, backups, scaling, troubleshooting and incident response — choosing the level of infrastructure the product actually needs.

AWS · EC2 · AUTO SCALING · RDS · LIGHTSAIL · CLOUDFRONT · LOAD BALANCING · CLOUDFLARE
04.1 — ARCHITECTURE

More than
a server.

For workloads that need room to grow, I have implemented AWS architecture with multiple layers working together rather than treating hosting as a single machine.

REPRESENTATIVE ARCHITECTURE · BASED ON INFRASTRUCTURE I HAVE IMPLEMENTED
01USERSRequests
→
02CLOUDFRONTDelivery
→
03LOAD BALANCERTraffic
→
AUTO SCALING
EC2
EC2
EC2
→
05RDSDatabase
MONITORINGVALIDATIONBACKUPSSECURITY
04.2 — RIGHT-SIZED

Architecture should fit
the problem.

Not every product needs the same infrastructure. Part of operating well is knowing when simplicity is an advantage and when additional resilience is justified.

LEAN

Lightsail

Practical cloud environments for sites where straightforward deployment, maintenance and predictable infrastructure are the priority.

SIMPLER FOOTPRINT
SCALE

EC2 + RDS

More flexible architecture when traffic, database separation, load distribution and horizontal scaling become important.

MORE MOVING PARTS · MORE CONTROL
EDGE

CloudFront / Cloudflare

Delivery, traffic management and protective layers that help improve resilience between users and the origin.

EDGE ORIGIN
DELIVERY + PROTECTION
04.3 — WHEN THINGS GO WRONG

Respond first.
Then learn from it.

I have dealt directly with attacks and service disruption: investigating abnormal activity, mitigating impact, restoring service and strengthening the environment afterward.

ACTIVITY
ANOMALY DETECTED
01

Detect

Monitor activity and recognize when behavior moves outside the expected pattern.

02

Investigate

Inspect what changed, where pressure is coming from and which layer is affected.

03

Mitigate

Reduce impact and protect the service while keeping the response proportionate to the incident.

04

Recover

Restore normal operation, validate the platform and confirm critical services are healthy.

05

Reinforce

Use what the incident revealed to improve resilience, monitoring and future response.

04.4 — OPERATIONS

Reliability is
continuous work.

Infrastructure is not finished after deployment. It needs visibility, maintenance and a way back when something changes unexpectedly.

01

Monitoring

Watching activity and system behavior so unusual conditions can be investigated instead of guessed at.

02

Backups

Maintaining recovery options and validating the operational pieces that protect continuity.

03

Migrations

Moving sites and services while accounting for data, configuration, DNS and continuity.

04

Validation

Checking the system after changes, recovery or deployment to make sure the experience still works end to end.

04.5 — THE PRINCIPLE

Build for today.
Prepare for change.

“Infrastructure is successful when the technology stays out of the way and the product remains available when people need it.”
DEPLOY→OBSERVE→PROTECT→RECOVER→ADAPT↻

FOUR DISCIPLINES. ONE CONNECTED WAY OF WORKING.

Build. Analyze. Improve.
Operate.

RETURN TO SELECTED WORK →