The following table compares and contrasts the traditional and serverless ways of developing and deploying applications:
| Parameter | Traditional | Serverless |
| Architectural style | Monolithic, SOA | Microservices-based |
| Time to market | Slower | Quicker time to market |
| Development velocity | Slow | Fast |
| Focus on core value proposition | Diffused | Laser focused |
| Infrastructure management overhead cost | High | Low |
| Deployment of code | Complex tooling | Simple as an upload of .zip or .tar.gz |
| Operational efficiency | Low | High |
Get Hands-On Serverless Applications with Kotlin now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.
Start your free trial Become a member now