Every new app should start serverless. When we built Adobe Creative Cloud, we had a ton of servers running on a fleet of custom linux vms. We had fleet management, custom auto-scaling, load tests before every new service deploy, custom Jenkins CI/CD, the works.
But most companies aren't Adobe, and can't afford to employ the horde of developers who had to come together to make that happen.
Today, you can get all the same benefits with a simple CLI tool. Type `npm install -g vercel`, `npx create-next-app`, and `vercel` at a command prompt, and you'll have your first serverless app deployed in minutes.
Serverless gives you:
* Reduced operational costs
* Increased developer productivity
* Increased reliability
Serverless doesn’t mean “no servers,” but you don’t need to manage servers because your APIs are granular cloud functions managed by your cloud provider.
No more worrying about Node, Apache, or HAProxy on Docker containers. Need something special? There are API service providers for just about everything, and they're usually better than your in-house crew because they're specialists dedicated to building tools.
Check out:
Vercel
Magic Labs
Fauna
Notion
Stripe
BigCommerce
Cloudinary
Ping me if you need help getting started with serverless.
Curious, what are some of the limitations or disadvantages if any for going serverless?