Thank for you signing up. Check your inbox for updates and access to the platform.
Get ready to go Serverless in Production with this 4 week course delivered by Yan Cui. This course takes you through building a production ready serverless website from testing, deployment, security right through to observability.
The motivation for this course is to give you hands-on experience building something with serverless technologies while giving you a broader view of the challenges you will face as the architecture matures and expands.
We will start at the basics and give you a firm introduction to Lambda and all the relevant concepts and service features, gradually ramping up and cover a wide array of topics such as API security, testing strategies, CI/CD, secret management, and operational best practices for monitoring and troubleshooting.
The course is kicked off covering the basics of building a Serverless application.
This includes an introduction to foundational services like Lambda, Cloud Formation, DynamoDB, API Gateway, Cognito, IAM and the Serverless Framework.
By the end of the week you would have deployed a basic Serverless application!
The second week dives into testing, integration and deployment of your Serverless application.
It starts with how and why you should approach testing Serverless applications differently, then dives into writing unit and integration tests for the Serverless application you build the previous week.
Finally at the end of the week the course will teach you how to setup CI/CD to continously test and deploy your Serverless application.
Week three brings us to asynchronous proccess of event data.
You'll get introduction to EventBridge and learn how to process events asynchronously, and how to test asynchronous event handlers.
You'll learn the differences between the various messaging and queueing mechanisms of AWS, from Kinesis, SNS, SQS, and EventBridge, and when to use them.
The week ends off with an overview of Orchestration vs Choreogrpahy and when to use one or the other.
In the final week of the course we learn how to operationalise your Serverless application.
It covers observability fundamentals, such as logging, from aggregation, structured logging through to log sampling, and distributed tracing using correlation IDs.
It includes useful real world tips on how to avoid costly mistakes and how to right size your functions.
The week closes out with a wrap up from Yan that covers everything you should have learnt over the duration of the course.
The class takes place over 4 weeks, with an average time commitment of 4 to 5 hours per week. Each week will follow this schedule:
Mondays: Lectures and learning exercise released within the Senzo platform; you'll need to be logged in to access this.
All week: Peer chat and exercise sharing via chat server with your Instructor and class cohort.
Mondays, 11am and 11pm CEST: Live recap and Q&A sessions (~1 hour) with the instructor, recap the week, exercise answers released.
Course materials are permanently available on the Senzo platform after they've been released, and you retain access in perpetuity.
If you are in any of the following roles, you'll benefit from this class:
Backend Engineers whose main focus is building business logic and managing APIs and data processing pipelines (which can include monitoring and being on-call as well).
DevOps engineers whose main focus is in managing the company’s AWS environment and shared infrastructures such as CI/CD, VPCs, IAM users/roles and sometimes general AWS security.
Security engineers whose main focus is in the overall security of the company’s application, which spans across application security, AWS security, CI/CD pipelines as well as incident management.
Fullstack engineers who have to dabble with both frontend and backend technologies and whom increasingly need to be fluent with AWS and its serverless offerings.
Tech Lead, Architects and Engineering Managers who want to get a deeper understanding of serverless technologies so they can better help their teams make the best architectural decisions and solve architectural challenges they face.