Jose Castillo

I built a self-healing AWS infrastructure using Terraform to automatically recover from failures and optimize reliability. This article walks through the architecture, key Terraform components, and lessons learned while designing for resilience and cost efficiency. Read the full breakdown below. #SelfHealing #HighAvailability #AWS #Terraform #DevOps #InfrastructureAsCode #Peabsmart Consulting https://lnkd.in/dceyYzWS

2

When a global e-commerce leader needed to escape the limits of legacy infrastructure, TEKsystems Global Services designed a repeatable AWS three-tier blueprint. Operations that once dragged on for hours now complete in minutes. AND Recovery Time Objective dropped below 4 hours. A foundation built for resilience and scale now powers the future of commerce. To read the full success story, visit: https://bit.ly/4mqW6hA

76

Did you know that the AWS command line tools use US-East-1 as their default region? If you don't specify a region or data center, your server, lambda, app, etc. are all running in US-East-1. Just thought I would remind folks to set their region in their command line and scripts.

7

1 Comment

Not all managed databases are created equal. 🎯Let me break down what actually matters when you're choosing between RDS MySQL and Aurora MySQL. The Architecture That Changes Everything RDS MySQL? Traditional storage architecture. Your data lives on EBS volumes attached to your instance. Aurora MySQL? Completely different game. It separates compute from storage, using a shared, distributed storage layer that automatically scales. Your data gets written to 6 copies across 3 Availability Zones simultaneously. That's not just redundancy—that's peace of mind. What This Means for Your Applications: ✅ Recovery Point Objective (RPO) under 1 second ✅ Recovery Time Objective (RTO) under 30 seconds ✅ Read replicas share the same storage (no lag from replication) ✅ Up to 15 read replicas vs RDS's 5 replicas limit ✅ 5x throughput of standard MySQL ✅ Automatic storage scaling up to 128TB Here's what surprised me most: Aurora can lose 2 copies of data without affecting write availability and 3 copies without affecting read availability. Try doing that with RDS. Aurora Global Database vs Regular Aurora ✅ Regular Aurora = perfect for single-region applications where you need high availability and performance. ✅ Aurora Global Database = your disaster recovery superhero. It replicates data across regions with dedicated infrastructure, typically with less than 1 second of lag. Secondary regions can be promoted in under 1 minute. When do I use which? Use Regular Aurora when: ✅ Single region deployment is sufficient ✅ You need HA within a region ✅ Budget is a primary concern Use Aurora Global Database when: ✅ You have a global user base ✅ Disaster recovery is critical ✅ You need read performance close to users worldwide ✅ Compliance requires multi-region data residency The catch? Cost. Aurora costs more than RDS, and Global Database adds another layer. But when you factor in the operational overhead you're avoiding and the performance gains you're getting, it often makes sense. What's your experience with Aurora? Have you made the switch? Drop your thoughts below. 👇 Follow me on LinkedIn: https://lnkd.in/dkeKb6cc #AWS #Aurora #MySQL #DatabaseArchitecture #CloudComputing #DevOps #CloudArchitecture #RDS #DisasterRecovery #ThePracticalArchitect

19

2 Comments

Federal teams running Kubernetes face a familiar challenge: rising costs, limited visibility. A new Vertosoft issue brief shows how IBM Kubecost delivers secure, in-cluster #FinOps for measurable savings and stronger budget confidence. Download: https://lnkd.in/ge2agCNY

9

Master Kubernetes with LearnKube's Advanced Kubernetes workshop! What should you expect? - Learn how to architect and design clusters from the ground up (in the cloud or on-prem). - Explore the Kubernetes internal component and how the system is designed with resiliency in mind. - Deep-dive into the networking components and observe the packets flowing into the cluster. - Hands-on labs to test the theory with real-world scenarios! - And more. The next course starts in September: https://lnkd.in/ge4aYVZq We also run in-person courses and private training: https://lnkd.in/g9N3m-Xr

11

Cloud innovation starts with strategy — not migration. Explore NetCom Learning’s Google Cloud Infrastructure Modernization Guide to lead the next wave of transformation.

5

I’ve been a DBA long enough to know that half the job is explaining why the job even exists. The other half is doing the work anyway. Lately, I’ve been navigating something new: GitLab, DevOps pipelines, IaC for RDS, and wiring automation with Ansible. None of this was in the "classic DBA handbook," unless you count the chapter titled "Please learn whatever the organisation ignores until they suddenly need it." So I’ve been learning on the job, not pretending to be an expert cuz everyday is new, not trying to compete with anyone, just trying to make the database world a little less chaotic. - Writing automation scripts. - Adding structure to DB changes via CD pipelines. - Turning RDS configurations into IaC so things stop living in someone’s memory. - Building pipelines so changes don’t depend on luck or screenshots. It’s new. It’s messy. I still Google things I shouldn’t admit. But it’s progress. If you’re a DBA caught between expectations and tools, and you’re not alone. We adapt. We learn. We keep the lights on even when no one notices. And honestly? That’s enough. #DBA #DevOps #GitLab #Ansible #RDS #IaC #LearningInPublic #TechLife

48

3 Comments