I’m a Principal Cloud Architect / Solutions Architect specializing in Oracle Cloud Infrastructure (OCI) and multicloud (AWS/Azure). I design and lead enterprise, mission-critical platforms—especially Oracle workloads (WebLogic + database ecosystems)—with a focus on resilience (HA/DR), security guardrails, observability, and operability at scale.

In customer-facing roles, I serve as the technical authority when it matters most: architecture decisions, executive-level conversations, and high-priority escalations for complex Oracle environments. I translate failure modes and risk into clear options, trade-offs, and action plans engineering teams can execute quickly.

🧠 What I Deliver (Enterprise Cloud / OCI):

• HA/DR architectures driven by RTO/RPO targets (design + DR runbooks + recovery readiness)
• Landing zones, governance, and security guardrails (IAM, network patterns, policy-as-code)
• Networking, identity, load balancing, and platform design for Oracle workloads
• Observability: metrics/logs/alerts, SLO-oriented dashboards, and incident response workflows
• Capacity planning, performance architecture, and cost optimization (FinOps)

I standardize delivery using Infrastructure as Code (Terraform) and automation (Python/Shell) to reduce operational risk, improve repeatability, and make platforms supportable—not just deployable.

🎯 Open to US-remote Principal / Lead Solutions Architect roles focused on OCI, mission-critical architecture, HA/DR, governance, and FinOps.

💎 “Good cloud architectures don’t just scale — they survive.”

Enterprise-grade OCI foundation for regulated and high-availability workloads

• Identity and access patterns (compartments, IAM policies, least privilege)
• Network architecture (VCNs, subnets, routing, segmentation) with standard patterns
• Guardrails and repeatability using Terraform (policy-as-code mindset)
• Designed for operability: logging/monitoring hooks, standardized naming/tagging

Reference architecture + DR runbooks for WebLogic and database ecosystems

• DR strategy aligned to RTO/RPO targets with clear trade-offs
• Runbooks for recovery readiness + validation drills
• Architecture decisions explained as failure-mode mitigation (not “because best practice”)
• Built to be supportable under pressure: “when everything’s on fire” clarity

Metrics/logs/alerts + SLO dashboards for operational excellence

• SLO-oriented dashboards and alerting that reduce noise and speed MTTR
• Incident workflows: triage, escalation paths, postmortems, and action tracking
• Focus on operability: “you can’t fix what you can’t see”

Cost optimization + performance architecture without breaking reliability

• Workload right-sizing guided by utilization and growth trends
• Cost allocation hygiene, operational guardrails, and practical savings levers
• Performance and cost treated as architecture inputs, not afterthoughts

🧩 “In mission-critical architecture, boring beats heroic every single time.” — Fernando Cuéllar