Previous Issues

---

Issue #236: Federated Serverless GraphQL 🌐

May 30, 2023

In this issue, AppSync merges APIs, Momento enables a Web SDK, and thanks to grandma, ChatGPT is no longer cool.

---

Issue #235: Cloudflare is coming for you, AWS!

May 23, 2023

In this issue, we recap Cloudflare's Developer Week, see lower latency from EventBridge, and get 7 hours of serverless innovation.

---

Issue #234: Is serverless the key to conversational programming? 🤔

May 16, 2023

In this issue, AI is on everyone's roadmap, we think about DynamoDB costs, and we converse about conversational programming.

---

Issue #233: A Prime example of when not to use serverless 🛑

May 9, 2023

In this issue, the Internet overreacts to sound architectural choices, AppSync goes private, and Ampt gets production ready.

---

Issue #232: Athena Provisioned Capacity 📈

May 2, 2023

In this issue, Athena gets provisioned capacity, Lambda supports Java 17, and Vercel announces Postgres and Redis options for frontend developers.

---

Issue #231: Blue checks or Bluesky? ✔️

April 25, 2023

In this issue, AWS Lambda (finally) gets Python 3.10, CodeCatalyst goes GA, and we think about value metrics.

---

Issue #230: A Bedrock Serverless Experience?

April 18, 2023

In this issue, AWS jumps on the Generative AI bandwagon, CodeWhisper goes GA, and someone puts the servers back in serverless.

---

Issue #229: Serverless life is but a stream 🚣

April 11, 2023

In this issue, AWS Lambda gets payload streaming support, S3 buckets get better default security, and serverless databases level up.

---

Issue #228: Lattice not worry about networking 🌐

April 4, 2023

In this issue, Amazon VPC Lattice goes GA, Cloudflare workers get more 'nodey', and SSM Parameter Store still reigns supreme.

---

Issue #227: The (diminishing) value of computer science 🧑‍💻

March 28, 2023

In this issue, SAM sync skips infra, Momento introduces Topics, and we discuss the future value of CS degrees.

---

Issue #226: Has "serverless" become meaningless? 🤔

March 21, 2023

In this issue, we get Amazon Linux 2023, Apache EventMesh graduates to a Top-Level Project, and we explore the meaninglessness of serverless.

---

Issue #225: The weary serverless traveler ✈️

March 14, 2023

In this issue, AWS Application Composer goes GA, we get some new heroes, and serverless PHP reaches another milestone.

---

Issue #224: Serverless Down Under 🦘🇦🇺

March 7, 2023

In this issue, I’m teaching serverless to kangaroos, Not-So-Serverless Neptune tries to redeem itself, and the SAM CLI gets a bit rusty.

---

Issue #223: Don't be fooled by serverless! 🙀

February 28, 2023

In this issue, Google Cloud helps you automatically reduce cold starts, we get some practical EventBridge Pipes advice, and we point out some flaws in anti-serverless arguments.

---

Issue #222: AWS accounts should be cattle 🐂

February 21, 2023

In this issue, AWS adds more account lifecycle controls, App Runner learns to share more, and serverless gets bash'd.

---

Issue #221: Serverless love is in the air ❤️

February 14, 2023

In this issue, asynchronous Lambdas get some much needed metrics, SAM Connectors (probably) took my advice, and we ask where serverless devs are spending their time.

---

Issue #220: Dude, where's my infrastructure? 🤷‍♂️

February 7, 2023

In this issue, your cloud resources get on the 'sam list', we learn about the state of serverless and edge databases, and we clear up some confusion about the future of cloud development.

---

Issue #219: Control is an illusion 🌀

January 31, 2023

In this issue, Amazon OpenSearch 'Serverless' goes GA, we look at some serverless DNA, and we ask just how much control you really need.

---

Issue #218: Is ChatGPT better at serverless than you? 🤖

January 24, 2023

In this issue, AWS SAM goes all linty, event-driven apps get some visuals, and we look at why ChatGPT is doing more harm than good.

---

Issue #217: Visual Designers, Serverless, and You! 🎨

January 17, 2023

In this issue, AWS Lambda gets a Maximum Concurrency for SQS, we learn the importance of 'first principle thinking', and we ponder the need for visual infrastructure design tools.

---