There’s one thing that will always fascinate me about the worldwide dev community:
Our ability to come up with solutions that consistently make our job less painful.
Because let’s be honest, some tasks that come with being a developer are… tedious.
Personally, something like maintaining servers always seems to be a pain in my a**. Not what I signed for at all.
That’s why I’m pretty pumped today to write about serverless architectures and why it’s a programming trend worth learning about.
As we already did for APIs and webhooks, this post serves as an introduction to the concepts behind serverless programming. I also crafted a small serverless app example to get a better understanding of it all.
- What does “serverless” mean
- Why serverless deserves your attention (benefits & limitations)
- What are the best use cases & tools
- How does it work (with Serverless & AWS Lambda example)
If you’re new to this, you should have a much stronger grasp on what the serverless “revolution” means to web development by the end of this post.
Let’s do this!
The first thing we have to get out of the way is understanding that serverless programming isn’t technically “serverless”.
→ Read the full post here
There are a lot of people who love both JS and UX/CSS. If we stop labeling people just as “JS developers” or “UX developers”, we can achieve a ceasefire in the current “JS vs. CSS” war and achieve a mutually benefiting peace.