Contents
Course Introduction
Serverless Survey
Course Conclusion
This course touches on the similarities and differences between AWS, GCP, and Azure serverless functions. The idea is to give you insight into what using the different offerings look like. The primary learning objective is to help you make an informed decision about which provider to use and if it fits your use case. The 30-minute course covers the three different providers (content largely taken from the comparing cloud platforms course--but cut down for content), deploying a sample application on each, and the ecosystem around deploying serverless applications. The provider lesson uses the same application and demonstrate deploying and other operational characteristics of each provider.
Intended Audience
- IT Pros
- Developers
Prerequisites
If you are not already familiar with serverless start with "Getting Started with Serverless Computing” before continuing with this course. You’ll also need some experience with cloud providers as well. Nothing specific is required, though you should have a general idea of how cloud computing works.
Learning Objectives
- Understand the state of serverless in 2017 List trade-offs between AWS, Google, and Microsoft platforms
- Learn to build, deploy, and run applications on the three platforms
- Learn open source tools for building serverless applications
This Course Includes
30 minutes of high-definition video.
What You'll Learn
Course Intro: What to expect from this course.
Serverless Overview: In this lesson, we’ll introduce you to the key players and prepare you for the hands-on demos in the following lessons.
AWS Lambda: In this lesson, you’ll learn about serverless on Lambda and deploy a Lambda function.
Azure Functions: In this lesson, we’ll discuss serverless Azure functions and learn how to deploy an HTTP function.
Google Cloud Functions: In this lesson, you’ll learn about serverless on Google Cloud and deploy an HTTP trigger function.
Ecosystems and Tools: In this lesson, you’ll learn about serverless framework and Apex.
Conclusion: A summary and review of what you have learned.
Hey, welcome to the Serverless Survey course. I'm Adam Hawkins, and I'm your instructor for this course. This course surveys the offerings from Amazon, Google, and Microsoft to prepare you for building serverless applications. The term serverless refers more to functions as a service. This is a new architecture style for modern applications, but do not let the name confuse you. Serverless does not mean there are no servers at all. Instead it means that servers are simply abstracted away from you. Now with serverless, you deploy individual functions or methods into the cloud and the provider handles the rest.
Consider a backend HTTP API. A serverless application may map HTTP requests to individual functions compared to a traditional model where one process handles all the requests. This architecture doesn't apply only to web applications. You can use it for async or event-driven architectures, web hooks, or generally anything that fits nicely into discrete units of work. This course prepares you to build, ship, and run applications on AWS Lambda, Azure Functions, and on top of Google Cloud Functions.
This is a survey course, so I'll cover the lay of the land, assess the different providers, and touch on what's happening in the serverless ecosystem. Here's the specific learning objectives. One, understand the state of serverless in 2017. Two, list trade-off between AWS, Google, and Microsoft platforms. Three, learn to build, deploy, and run applications on the three platforms. Four, learn open source tools for building serverless applications. And five, set you on the next steps on your serverless learning path.
You'll need some context before jumping into the course. Here's a quick checkpoint. Are you familiar with the term serverless? If so, great, this is the course for you. If not, then I suggest you start with the Getting Started with Serverless Computing course before continuing with this course. You'll also need some experience with the cloud providers as well, but nothing specific is required, though you should have a general idea of how cloud computing works. Finally, I'll do all of the demos using Node.js, but don't worry if you're not familiar with JavaScript. The coded examples will be no more than a dozen lines. So, my friend, sound good? Let's start off our survey by comparing the different providers.
Adam is backend/service engineer turned deployment and infrastructure engineer. His passion is building rock solid services and equally powerful deployment pipelines. He has been working with Docker for years and leads the SRE team at Saltside. Outside of work he's a traveller, beach bum, and trance addict.