I used to deploy Node.js apps on EC2 and manage servers like it was my second job.

Port configs. PM2 restarts. Nginx rewrites. SSL renewals.

Then I ran my first AWS Lambda function.

80% of that work is gone.

Here's what Lambda actually does that nobody explains clearly:

1. → You write a function
2. → AWS runs it ONLY when triggered
3. → You pay for milliseconds of execution
4. → It scales from 1 to 1,000,000 requests without you touching anything

As a full-stack developer in Bahrain, preparing for my AWS Developer Associate exam, this is the shift that changes how you think about backend architecture.

Not "how do I manage a server" but "what should happen when this event fires."

That mental model switch took me a week to fully get.

I'm documenting everything as I study.

Drop a 🔥 if you want me to share my Lambda notes weekly.