Tech Lead Journal cover image

#168 - Serverless as a Game Changer - Joseph Emison

Tech Lead Journal

NOTE

Exploring Code Liability and Defining Serverless

Code is considered a liability and includes not only application code but also infrastructure code and configuration. Domain-specific languages for infrastructure like YAML and CloudFormation are categorized separately due to low maintenance costs when done correctly. Using tools like Pulumi or CDK as infrastructure code requires more maintenance compared to YAML. Serverless is defined as not managing uptime, focusing on differentiated code, utilizing managed services like Lambda, DynamoDB, Cognito, and AWS AppSync. A serverless architecture involves delegating most of the infrastructure responsibilities to managed services, such as AWS. Leveraging services like Firebase is preferred for simpler applications, while AWS services are more suitable for robust applications like financial services. The essence of serverless lies in being responsible for code functionality and not uptime, promoting the use of managed services for a more efficient and beneficial architectural approach.

00:00
Transcript
Play full episode

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.
App store bannerPlay store banner