Serverless architectures: What, why, why not, and where next?
Mike Roberts expands on the ideas from his Introduction to Serverless keynote to give a cautiously optimistic description of the state of the art of the serverless world, concluding with how its expected to develop over the coming months and years.
| Talk Title | Serverless architectures: What, why, why not, and where next? |
| Speakers | Mike Roberts (Symphonia) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | New York, New York |
| Date | April 3-5, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Cloud computing has reduced engineering costs and improved delivery effectiveness drastically over the last decade, but new systems and features can still see lead times of weeks or months even for a prototype release, and operations costs are still often inefficiently managed. Modern approaches in cloud computing, including the new area of serverless architectures, tackle both of these concerns. Serverless architectures are those that incorporate third-party backend-as-a-service (BaaS) products into the application or that use functions-as-a-service (FaaS) platforms, like AWS Lambda, to run server-side code in fully managed, event-driven, ephemeral containers. By using these ideas, and by moving much application behavior to the frontend, such architectures remove much of the need for the traditional “always on” server system sitting behind a frontend client. Depending on the circumstances such systems can significantly reduce operational cost and increase the speed of experimentation. However the flip side sees extended vendor dependencies and (at present) immature supporting services. Mike Roberts expands on the ideas from his Introduction to Serverless keynote to give a cautiously optimistic description of the state of the art of the serverless world, concluding with how it’s expected to develop over the coming months and years.
