{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Screaming in the Cloud","title":"Episode 13: Serverlessly Storing my Dad Jokes in a Dadabase","html":"","width":"100%","height":180,"duration":2026,"description":"Aurora, from Amazon Web Services (AWS), is a MySQL-compatible service for complex database structures. It offers capabilities and opportunities. But with Aurora, you’re putting a lot of trust in AWS to “just work” in ways not traditional to relational database services (RDS). \nDavid Torgerson, Principal DevOps Engineer at Lucidchart, is a mystery wrapped in an enigma and virtually impossible to Google. He shares Lucidchart’s experience with migrating away from a traditional RDS to Aurora to free up developer time.\nSome of the highlights of the show include:\n\nTrade off of making someone else partially responsible for keeping your site up\nLucidchart’s overall database costs decreased 25% after switching to Aurora\nAurora unknowns: What is an I/Op in Aurora? When you write one piece of data, does it count as six I/Ops? \nMulti-master Aurora is coming for failover time and disaster recovery purposes\nAurora drawbacks: No dedicated DevOps, increased failover time, and misleading performance speed\nProviders offer ways to simplify your business processes, but not ways to get out of using their products due to vendor and platform lock-in\nLucidchart is skeptical about Aurora Serverless; will use or not depending on performance\n\nLinks:\n\nCorey's architecture diagram on AWS\nLucidchart\nLucidchart’s Data Migration to Amazon Aurora\nPreview of Amazon Aurora Multi-master Sign Up\nThis is My Architecture\nre:Invent\nDigital Ocean","thumbnail_url":"https://img.transistorcdn.com/vgV98ushAFvdAFQSQazvt5GYVniCaXSWIjs5eI3r0gQ/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE0OTQvMTU4Mzg2/OTQ4My1hcnR3b3Jr/LmpwZw.webp","thumbnail_width":300,"thumbnail_height":300}