Moving from Lambda ƛ to Azure Functions <⚡>
“It’s time to migrate.”
Maybe the decision to switch cloud providers came “down from above.” Maybe the decision was yours. Perhaps your original solution was merely a spike to “kick the tires” of one cloud, and now it’s time to try another. Whatever your reasons, if you are considering moving your serverless functions from AWS Lambda to Azure Functions, you’re in the right place to learn how!
“Moving from Lambda to Azure Functions” is a six-part videos series that covers what you need to know to make the transition between cloud providers. You’ll learn how to migrate your app, explore how resources in Azure relate to Amazon AWS, build a function locally, deploy it manually and learn how to push it automatically as part of a CI/CD pipeline.
The Sample App
You can view the source code for the sample app and deploy the migrated code directly to Azure with a single-click in the “AWSMigration” GitHub repository.
This is the source code for the "Moving from Lambda to Azure Functions" video series that demonstrates how to migrate…
The first video provides and overview of the sample application and shows how to test and access it from the portal and the command line.
Create an Azure Functions App
The next video walks through how to create an Azure Functions app: the solution for hosting serverless functions in Azure.
Integrate Code and Implement Cache
Learn how to migrate the code and move from using Amazon DynamoDB to Azure’s inexpensive and easy-to-use Azure Table Storage for the application cache.
After the app is migrated and deployed, review how Azure resources are organized and accessed compared to Amazon AWS.
Build, Test, Run and Deploy from your Local Machine
Use the cross-platform Azure Functions Core Tools to create a local functions project and run it. Then, using free and cross-platform Visual Studio Code, build and debug a project in just a few short steps. After implementing the fully migrated function, deploy it to Azure directly from Visual Studio Code.
Review Advanced Features: Security, CI/CD (DevOps) and More
Friends don’t let friends right-click publish. That’s why in this final video we’ll make your DevOps team proud by implementing continuous deployment. The function will also get a security lift in two areas: first, it will require authentication for access. Second, it will get assigned a managed identity to securely access other resources and assets.
This is a short series designed to ease your understanding of how to migrate from AWS Lambda to Azure. As always, we welcome your feedback, comments, and suggestions. If you have experienced a similar migration, please share your thoughts and tips in the comments below!
What’s next? Check out an Overview of Azure Functions.