The AWS Morning show you never knew you wanted

AWS Morning Brief for the week of May 4, 2020.

Join me as I continue a new series called Whiteboard Confessional by exploring the time I sent out a newsletter to 18,000 people filled with broken links (yep, it was the other day)—and what I did to fix them without sending out an updated version. In this podcast, I also talk about what my email newsletter architecture looks like, how I use analytics to continuously optimize Last Week in AWS, why not all data is good data, what I am not interested in knowing about my readers, what I did to answer questions that my email marketing platform didn’t answer for me, how that ended up breaking things briefly, how I fixed what was broken, and more.

AWS Morning Brief for the week of April 27, 2020.

Join me as I continue a new series called Whiteboard Confessional by focusing on the wild world of databases and touching upon three-tiered web apps, how scaling an app to 200 million users is a massive challenge, the time Corey’s boss suggested running a database on top of NFS, why modern cloud architecture is a much better approach than using NFS, the genesis of why Corey tends to see many things as a database (ahem, Route 53), why you should avoid NFS for greenfield designs, and more.

AWS Morning Brief for the week of April 20, 2020.

Join me as I continue a new series called Whiteboard Confessional with a look at the rise of microservices and some of the reasons why people started breaking apart monoliths in the first place, why microservices can be a great approach to software development, how Hacker News took the wrong lessons from microservices and encouraged devs from 15-person startups to embrace them at their own peril, why Google would argue that its own internal systems shouldn’t look like Google’s internal systems, how microservices make platforms much harder to scale, why you shouldn’t necessarily hop on the latest software development trends just because, and more.

AWS Morning Brief for the week of April 13, 2020.

Join me as I continue a new series called Whiteboard Confessional with a look at the importance of the T-shaped engineer and how they can drive lots of revenue, where T-shaped engineers fall short, how becoming an expert in one specific tool can be a good thing at first but will almost certainly cause problems down the road (e.g., when you leave the company), how technologies like serverless and Kubernetes are the zeitgeist of today and why that may end up hurting companies tomorrow, who the worst developer Corey’s ever come across is, why you should think twice about pushing your favorite tools on the rest of your team, and more.