Building maintainable, observable applications on multicloud serverless architecture

Description

Serverless computing has a number of obvious benefits over traditional application infrastructure—you pay only for what you use, scale up or down immediately to match supply with demand, and avoid operating any server infrastructure at all. However, implementing maintainable and scalable applications using serverless computing services like AWS Lambda or Google Cloud Functions poses a number of challenges. The absence of long-lived, user-managed servers means that states cannot be maintained by the service. Longer function invocation times (referred to as cold starts) become very important to track because they impact the response time of the service and will impose additional cost. Additionally, the transition to smaller individual components (much like breaking a monolithic application into microservices) results in a simpler deployment model but makes the system as a whole increasingly complex.

With increasing adoptions of multiple cloud providers for redundancy and resiliency, use of serverless architecture needs to now be adjusted to work seamlessly across various providers. Park Kittipatkul details patterns and best practices around architecting and implementing code in serverless environments, specifically how to build maintainable serverless code and minimize the occurrence of cold starts. He also explains how to properly instrument applications and supporting services so your systems remain easily observable. And you’ll leave with fresh considerations and techniques for how to build and maintain multicloud serverless services.