You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/migration/lambda-functions-migration-migrate.md
+49-42Lines changed: 49 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ To update code for Azure Functions runtime requirements:
23
23
24
24
- Use the [Functions extensions bundle](/azure/azure-functions/functions-bindings-register) to handle various bindings and triggers that are similar to AWS services. For .NET applications, you should use the appropriate NuGet packages instead of the extensions bundle.
25
25
26
-
- The extensions bundle allows you to integrate with other Azure services such as Storage, Service Bus, and Azure Cosmos DB without needing to manually configure each binding through SDKs. For more information, see [Connect functions to Azure services by using bindings](/azure/azure-functions/add-bindings-existing-function) and [Azure Functions binding expression patterns](/azure/azure-functions/functions-bindings-expressions-patterns).
26
+
- Use the extensions bundle to integrate with other Azure services such as Storage, Service Bus, and Azure Cosmos DB without needing to manually configure each binding through SDKs. For more information, see [Connect functions to Azure services by using bindings](/azure/azure-functions/add-bindings-existing-function) and [Azure Functions binding expression patterns](/azure/azure-functions/functions-bindings-expressions-patterns).
27
27
28
28
The following snippets are examples of common SDK code. The AWS Lambda code maps to the corresponding triggers, bindings, or SDK code snippets in Azure Functions.
29
29
@@ -245,7 +245,7 @@ The following snippets are examples of common SDK code. The AWS Lambda code maps
245
245
246
246
:::column-end:::
247
247
:::column span="":::
248
-
248
+
249
249
Azure Functions code (Trigger)
250
250
251
251
```
@@ -363,68 +363,75 @@ These resources provide specific examples and detailed steps to facilitate the m
363
363
364
364
## Deploy and test the application
365
365
366
+
Perform a guided migration of workloads to Azure Functions, and test the deployed functions to validate their performance and correctness.
367
+
366
368
### Deploy to Azure
367
369
368
-
Deploy with the [Visual Studio Code](/azure/azure-functions/functions-develop-vs-code#publish-to-azure) publish feature, or from the command line using [Azure Functions Core Tools](/azure/azure-functions/functions-run-local#project-file-deployment) or the [Azure CLI](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip). Our [Azure Dev Ops Task](/azure/azure-functions/functions-how-to-azure-devops#deploy-your-app) and [GitHub Actions](/azure/azure-functions/functions-how-to-github-actions) similarly leverage One deploy.
370
+
Deploy workloads by using the [VS Code](/azure/azure-functions/functions-develop-vs-code#publish-to-azure) publish feature. You can also deploy workloads from the command line by using [Azure Functions Core Tools](/azure/azure-functions/functions-run-local#project-file-deployment) or the [Azure CLI](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip). [Azure DevOps](/azure/azure-functions/functions-how-to-azure-devops#deploy-your-app) and [GitHub Actions](/azure/azure-functions/functions-how-to-github-actions) also use One Deploy.
371
+
372
+
- Azure Functions Core Tools: [Deploy your function app](/azure/azure-functions/flex-consumption-how-to#deploy-your-code-project) by using [Azure Functions Core Tools](/azure/azure-functions/functions-run-local) with the `func azure functionapp publish <FunctionAppName>` command.
373
+
374
+
- Continuous integration and continuous deployment (CI/CD) pipelines: Set up a CCI/CD pipeline by using services like GitHub Actions, Azure DevOps, or another CI/CD tool.
369
375
370
-
- Azure Functions Core Tools
371
-
- [Deploy your function app](/azure/azure-functions/flex-consumption-how-to#deploy-your-code-project) using [Azure Functions Core Tools](/azure/azure-functions/functions-run-local)with the following command: `func azure functionapp publish <FunctionAppName> `
376
+
For more information, see [Continuous delivery by using GitHub Actions](/azure/azure-functions/functions-how-to-github-actions) or [Continuous delivery with Azure Pipelines](/azure/azure-functions/functions-how-to-azure-devops).
372
377
373
-
- CI/CD Pipelines
374
-
- Set up a Continuous Integration/Continuous Deployment (CI/CD) pipeline using services like GitHub Actions, Azure DevOps, or another CI/CD tool.
375
-
- Refer to [this guide for GitHub Actions](/azure/azure-functions/functions-how-to-github-actions) or [this guide for Azure DevOps](/azure/azure-functions/functions-how-to-azure-devops).
378
+
### Perform end-to-end testing
376
379
377
-
### Perform End-to-End Testing:
380
+
- Validate functionality
378
381
379
-
- Validate Functionality
380
-
- Test each function thoroughly to ensure it works as expected. This includes verifying input/output, event triggers, and bindings.
381
-
- Use tools like curl or [REST Client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) extension on VS Code to send HTTP requests for HTTP-triggered functions.
382
-
- For other triggers, such as timers or queues, ensure the triggers fire correctly and the functions execute as expected.
382
+
- Test each function thoroughly to ensure that it works as expected. These tests should include input/output, event triggers, and bindings verification.
383
+
384
+
- Use tools like curl or [REST Client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) extensions on VS Code to send HTTP requests for HTTP-triggered functions.
385
+
386
+
- For other triggers, such as timers or queues, ensure that the triggers fire correctly and the functions run as expected.
387
+
388
+
- Validate performance
383
389
384
-
- Validate Performance
385
390
- Conduct performance testing to compare the new Azure Functions deployment with the previous AWS Lambda deployment.
386
-
- Monitor metrics like response time, execution time, and resource consumption.
387
-
- Utilize Azure Application Insights for [monitoring, log analysis, and troubleshooting](/azure/azure-functions/functions-monitoring) during the testing phase.
388
391
389
-
- Troubleshoot using Diagnose and Solve Problems
390
-
- Leverage the [Diagnose and Solve Problems](/azure/app-service/overview-diagnostics) feature in the Azure Portal to troubleshoot your Function App.
391
-
- This tool provides a set of diagnostics features that can help you quickly identify and resolve common issues such as application crashes, performance degradation, and configuration problems.
392
-
- Follow the guided troubleshooting steps and recommendations provided by the tool to address identified issues.
392
+
- Monitor metrics like response time, run time, and resource consumption.
393
+
394
+
- Use Application Insights for [monitoring, log analysis, and troubleshooting](/azure/azure-functions/functions-monitoring) during the testing phase.
393
395
394
-
## Optimize and Monitor
396
+
- Troubleshoot by using the diagnose and solve problems feature
395
397
396
-
Follow these steps to effectively monitor, troubleshoot, and optimize your Azure Functions for performance and cost.
398
+
Use the [diagnose and solve problems](/azure/app-service/overview-diagnostics) feature in the Azure portal to troubleshoot your function app. This tool provides a set of diagnostics features that can help you quickly identify and resolve common problems, such as application crashes, performance degradation, and configuration problems. Follow the guided troubleshooting steps and recommendations that the tool provides to address problems that you identify.
397
399
398
-
### Use Azure Application Insights for Monitoring and Troubleshooting
400
+
## Optimize and monitor the application's performance
399
401
400
-
- Set Up Application Insights
401
-
- Enable [Azure Application Insights](/azure/azure-functions/functions-monitoring) for your Azure Functions to collect detailed telemetry data for monitoring and troubleshooting. Application Insights can be enabled through the Azure Portal or in the function app's host.json configuration file.
402
+
Follow these steps to effectively monitor, troubleshoot, and optimize your function app for performance and cost.
402
403
403
-
- Collect Telemetry Data
404
-
- Application Insights provides various telemetry data such as request logs, performance metrics, exceptions, dependencies, and more.
404
+
### Use Application Insights for monitoring and troubleshooting
405
405
406
-
- Analyze Logs and Metrics
407
-
- Access the Application Insights dashboard from the Azure Portal to visualize and analyze logs, metrics, and other telemetry data.
408
-
- Utilize the built-in tools for creating custom queries and visualizing data to gain insights into the performance and behavior of your Azure Functions.
406
+
Enable [Application Insights](/azure/azure-functions/functions-monitoring) for your function app to collect detailed telemetry data for monitoring and troubleshooting. You can enable Application Insights through the Azure portal or in the function app's host.json configuration file. After you enable Application Insights, you can:
409
407
410
-
- Set Up Alerts
411
-
- Configure alerts in Application Insights to notify you of critical issues, performance degradation, or specific events. This helps in proactive monitoring and timely response to problems.
408
+
- Collect telemetry data. Application Insights provides various telemetry data such as request logs, performance metrics, exceptions, and dependencies.
412
409
413
-
### Optimize for Cost and Performance
410
+
- Analyze logs and metrics. Access the Application Insights dashboard from the Azure portal to visualize and analyze logs, metrics, and other telemetry data. Use the built-in tools to create custom queries and visualize data to gain insights into the performance and behavior of your function app.
411
+
412
+
- Set up alerts. Configure alerts in Application Insights to notify you of critical problems, performance degradation, or specific events. These alerts help you proactively monitor and quickly respond to problems.
413
+
414
+
### Optimize for cost and performance
415
+
416
+
- Scaling and performance optimization:
417
+
418
+
- Use autoscaling features to handle varying workloads efficiently.
419
+
420
+
- Optimize function code to improve performance by reducing run time, optimizing dependencies, and using efficient coding practices.
414
421
415
-
- Scaling and Performance Optimization
416
-
- Use autoscaling features available to handle varying workloads efficiently.
417
-
- Optimize function code to improve performance by reducing execution time, optimizing dependencies, and using efficient coding practices.
418
422
- Implement caching strategies to reduce repeated processing and latency for frequently accessed data.
419
423
420
-
- Cost Management
421
-
- Use the [Azure Cost Management and Billing](/azure/cost-management-billing/cost-management-billing-overview) tools to monitor and analyze your Azure Functions costs.
422
-
- Set up budgeting and cost alerts to manage and predict expenses effectively.
424
+
- Cost management:
425
+
426
+
- Use the [Microsoft Cost Management](/azure/cost-management-billing/cost-management-billing-overview) tools to monitor and analyze your Azure Functions costs.
427
+
428
+
- Set up budgeting and cost alerts to manage and predict expenses effectively.
429
+
430
+
## Get started
423
431
424
-
## Get Started
432
+
Use the [MigrationGetStarted repo](https://github.com/MadhuraBharadwaj-MSFT/MigrationGetStarted) as a template to begin your proof of concept. This repo includes a ready-to-deploy Azure Functions project that has the infrastructure and source code files to help you get started.
425
433
426
-
- Use this [GitHub repo](https://github.com/MadhuraBharadwaj-MSFT/MigrationGetStarted) as a starter template to begin your PoC migration. This is a ready-to-deploy Functions project that has the necessary infrastructure (bicep) and source code files to help you get started.
427
-
- If you prefer to use Terraform instead, use this [GitHub repo](https://github.com/MadhuraBharadwaj-MSFT/MigrationGetStarted-Terraform)
434
+
If you prefer to use Terraform, use [MigrationGetStarted-Terraform](https://github.com/MadhuraBharadwaj-MSFT/MigrationGetStarted-Terraform) instead.
0 commit comments