Just finished this article and then today Microsoft goes down worldwide.

So I don't get it. How is serverless supposed to be the future if services go down ALL the time?

Was playing around with lambda and found an edge case where state is retained. Thought people might be interested. https://medium.com/@thomas.mcnicol/unexpected-aws-lambda-behaviour-7109da2d38f

We started using Lambda the right way — async, event-driven, retry-friendly workloads. Then it slowly crept into latency-sensitive API paths. That's when things got messy.

What we ran into:

- Cold starts hitting user-facing requests on low-QPS and spiky-traffic APIs

- One-invocation-per-environment model quietly exhausting downstream connection pools at scale

- Provisioned concurrency helping, but shifting us back into capacity planning territory

- VPC attachment adding more operational complexity than we'd accounted for

- Observability gaps — healthy invocation rate ≠ healthy service

The fix wasn't "stop using Lambda." It was getting honest about which workloads need elasticity vs. which need predictability. Those are different requirements, and the same execution model doesn't serve both.

https://dashbird.io/blog/serverless-enforces-useful-engineering-practices/

❓Is serverless actually cheaper?
❓How do I lower my serverless costs?
❓Why is AWS so expensive?

We address all these questions and more in our latest article - The Great Serverless Cost Debate

Here are some of the key points we covered:

• 💪The best part of serverless infrastructure is that you only pay when your users are online. Your business will have as much computing power as it needs without buying new equipment when you grow.

• 💪With AWS Lambda your first million requests are free. So are the 400,000GB seconds of computing time that come with every account.

• 💪Serverless trackers should be used to not only have an overview of how your functions are doing, but to also see costs incurred.

• 💪Serverless = outsourcing servers

If you haven't made the transition, there is no better time to switch to serverless!

When I first heard about Webiny around 2 years ago, I knew it had potential. I was drawn specifically to the fact that it was serverless because I was already investigating the concept and was drawn to it believing it was the future of software engineering.

Having joined the team 6 months ago, we're still struggling to get over the hurdle of explaining why Webiny is so good, and we think it's largely because they don't understand serverless, or are actually afraid of the concept.

We're slightly changing our position to be what we call a "CMS+", because there's a lot of features Webiny comes with that are largely because of serverless (CDNs, DNS, better security, DDoS protection, to name a few) that can't easily be understood without further explanation, and we're hoping that the "plus" sign opens up more discussion about those features.

I just published this article on the subject, and I'd be glad of your thoughts about it:

https://www.webiny.com/blog/introducing-webiny-enterprise-headless-cms-plus

We also just launched this campaign on Product Hunt today, the link is on that page. Thanks for your comments everyone.

Hey everyone,

I've just written a blog post about a major shift in my approach to AWS serverless development, and I'm eager to share it with this community.

🔗 https://medium.com/p/9003216865cd

For a long time, I was a staunch supporter of traditional, local serverless development. It was familiar, it was comfortable - but it also had its limits. That all changed when I decided to dive headfirst into a cloud-centric workflow.

In my post, I talk about:

• Why I moved away from local AWS development and the challenges I faced.

• How embracing cloud-based tools, especially Jupyter Notebooks, revolutionized my workflow.

• The benefits I've reaped from this shift – think agility, efficiency, and a deeper understanding of AWS capabilities.

I've found this new approach to be a total game changer, making my work more efficient and enjoyable. But I'm curious to know about your experiences too!

➡️ How have you adapted your AWS workflows? Are you still sticking with traditional methods, or have you also made the leap to more cloud-native practices?

I'm looking forward to reading your thoughts and stories!

This week, we have published more than 50+ articles in Towards AWS. Here are some of the featured articles we have collected for you. Enjoy and keep learning.

Read here: https://towardsaws.com/best-of-towards-aws-may-2021-78ae7b1c9de6

Hi all i followed this tutorial to set my domain for an angular 6 serverless project:

https://serverless.com/blog/serverless-api-gateway-domain/

My domains dont seem to work or serve the webpages correctly

This domain seem to work but its just blank:

https://10mindates.io/

These domains gives an error:

10mindates.io

http://10mindates.io/

http://10mindates.io/

http://www.10mindates.io/

https://www.10mindates.io/

This is my production domain,which works:

https://bczg9hixxd.execute-api.ap-southeast-1.amazonaws.com/production/

For the certificate manager ive issued 2 certs:

10mindates.io

*.10mindates.io

For the API gateway custom gateway ive added the correct base mapping (im using regional)