Blaize Stewart

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

I’ve been running a multi-model AI workflow for a while now, and it’s changed how I build software. Instead of chasing the “best” model, I use role separation: Architect → Constructor → Evaluator. I wrote up the framework I’ve been using in this article: The ACE Framework. If you’re working with multiple models already, this may resonate. If not, you might want to start.

8

6 Comments

Grow engineering velocity without growing the security backlog. Build security into every commit so code ships safely, no matter whether it’s written by humans or AI.

3

Lock down your Tiger Data services, without the overhead of a VPC. Here’s a quick walkthrough of using IP Allow Lists to control access to just trusted networks.

14

▶️ Concept Models (Pt 3): Concept Model enabling other artifacts - Example Due to interest from my previous post/presentation, this is the final part of a short series that will go into more detail on Concept Models and how they can fit in with a bigger picture. Pt 1 was defining what a Concept Model (CM) was. Pt 2 was Aligning Business Architecture & Data. 🎉 We have arrived!! Part 3 shows an example of a scoped Concept Model aligned to the same scope portion of the Info Concept Map, then aligned to two value streams which use these concepts as entrance and exit criteria for movement. (Graphic) - Use the Concept Model with business stakeholders for high level understanding of the scope of concepts and how they relate. - Validate the definitions, states and types of those concepts with the business stakeholders, which creates the Info Concept Map. - Map those concepts to your value streams to give them context and validate the states of the concepts/data you will need for tracking! - Use all 3 of these when you collaborate with data stakeholders to provide scope and context they can then use to do more detailed maps and models they need! 🌟 The beauty of using these artifacts when aligning business architecture to data is all of these concepts (the 'what') in context (the 'why') will give factual business meaning to the data needed for true business value! This is where the collaboration between these architecture domains begins! #businessarchitecture #businessanalysis

115

8 Comments

This is a good (long form) article covering the specifics of the role “Foward Deployed Engineer”. The article provides a contrast with the Solutions Architect role. https://lnkd.in/eC-9shhc

1