Title: Issue #66: Do You Destroy Your Stacks?
Publication: Ready, Set, Cloud!
Series: Ready, Set, Cloud Picks of the Week
Author: Allen Helton
Published: July 03, 2023
URL: https://www.readysetcloud.io/newsletter/66/

We learn how to destroy unused developer stacks and figure out how to detect AI-generated content in this week's issue


### Serverless Superhero

Our serverless superhero this week is [Ro Ndimofor](https://twitter.com/atehrosius), developer at [Serverless Guru](https://twitter.com/serverlessguru) and AWS serverless hero. Ro is a great writer, often writing about Step Functions (my favorite service), CDK, and AppSync on [his blog](https://phatrabbitapps.com/). Thank you, Ro, for being a wonderful role model and educator!

### Interesting Reads

We know it's important with serverless applications to design for retry. *Everything fails all the time*, so we need to account for it! [Ran Isenberg](https://twitter.com/IsenbergRan) published a blog post on [API idempotency using AWS Lambda powertools](https://www.ranthebuilder.cloud/post/serverless-api-idempotency-with-aws-lambda-powertools-and-cdk). He breaks down the architecture of an idempotent endpoint, then shows how to build it with the CDK. Ran goes on to show two different implementations for idempotency checking and offers his recommendation on how to approach it yourself.

[Lee Gilmore](https://twitter.com/LeeJamesGilmore) provided us with a sobering article last week asking if [serverless lock-in and spiraling complexity are worth it](https://blog.serverlessadvocate.com/the-conundrum-of-serverless-lock-in-spiralling-complexity-is-it-all-worth-it-b194ce9df294). He talks about the good and bad, comparing what software development was 10 years ago vs today. He also brings up the many components of a production-ready serverless application, casting away the "serverless is simple" myth. No spoilers here - this is a great read where he determines if serverless is worth it given the baggage.

There was an AI hackathon recently that drew the attention of a powerhouse group of people. [Matt Morgan](https://twitter.com/NullishCoalesce), [Julian Michel](https://www.linkedin.com/in/julianmichel2/), [Johannes Koch](https://twitter.com/Lockhead), and [Danielle Heberling](https://twitter.com/deeheber) grouped up to [create the AWS Speakers Directory](https://dev.to/aws-builders/presenting-aws-speakers-directory-an-ai-hackathon-project-19je) using a slew of AWS serverless services and AI tools. In the post, Matt talks about the project, why they made certain decisions, and even provides detail about their data model. It's a super cool breakdown of a tremendous build.

I'm a big fan of ephemeral environments. Spin one up when you need it, destroy it when you don't. This helps prevent drift in a dev environment and guarantees you're always starting fresh with whatever is in your `main` branch. [Matt Martz](https://twitter.com/martzcodes) has been making some wonderful advances in this paradigm. In a post from last week, he introduced [the destroyer stack](https://matt.martz.codes/destroy-their-stacks-ephemeral-cdk-stacks-as-a-service) which is a centralized destruction mechanism that deletes resources that aren't in use. It's all triggered off a configurable TTL and backed behind the `@aws-community/ephemeral` package to use directly in your CDK applications.

[Yan Cui](https://twitter.com/theburningmonk) published an article last week that made me scratch my head. He poses the question ["are we getting infrastructure all wrong in the serverless era?"](https://theburningmonk.com/2023/06/are-we-getting-infrastructure-all-wrong-in-the-serverless-era/) It's a great question where he poses a few good fundamental points on infrastructure and how we consider it as it relates to business logic. This one is a puzzler and I expect we'll get a polarizing response from it.

### Podcasts

Episode 13 of the [Ready, Set, Cloud podcast](https://readysetcloud.io/podcast/13) released last week with [Alex Kearns](https://www.linkedin.com/in/alexjameskearns). Alex and I discuss app modernization and cloud migration. We cover what the difference is, some strategies around getting into the cloud, and how to beat modernization paralysis.

### New Releases

S3 now [provides restore status of Glacier objects](https://aws.amazon.com/about-aws/whats-new/2023/06/amazon-s3-restore-status-s3-glacier-objects-list-api/) when using the List API. Since loading things out of Glacier is an async process, this will provide a nice way to inform users how far along you are when doing a retrieval.

### Spotlight

The internet is constantly buzzing about generative AI and all the new things you can do with it. We're treading into dangerous territory where it's hard to determine if something is created by a human or by AI (don't worry, my newsletter is still written by hand). [Stephen Sennett](https://twitter.com/ssennettau) wrote a delightful article on how he [built a serverless AI content detector](https://dev.to/ssennettau/building-a-serverless-ai-content-detector-65d). He walks through his creative process and details exactly how he built it. It's a fun read with lots of pictures and humor throughout.

### Tip of the Week

The Lambda godfather, [Julian Wood](https://twitter.com/julian_wood), released a 23-part video series on Lambda fundamentals last week. This is something we all have a chance to learn a few things about one of our favorite services.



### Last Words

Do you use Lambda layers? I feel like everyone who uses them has a different motivation. If you do, reach out and tell me how and why. If you don't, I'm curious as to why not. Send me an email or reach out on Twitter!

If you'd like to make a recommendation for the serverless superhero or for an article you found especially useful, send me a message on [Twitter](https://twitter.com/allenheltondev), [LinkedIn](https://www.linkedin.com/in/allenheltondev/), or [email](mailto:allenheltondev@gmail.com).

Happy Coding!

Allen