Build serverless APIs with Azure Functions | Azure Friday
Vložit
- čas přidán 2. 07. 2024
- Jeff Hollan joins Scott Hanselman to show how you can build highly scalable serverless APIs with Azure Functions.
0:00 - Overview
1:09 - What "serverless" really means
4:00 - A closer look at Azure Functions
7:29 - Azure Functions Live Metrics
10:45 - Thinking downstream of Azure Functions
13:52 - Using deployment slots with Azure Functions
15:56 - Wrap-up
◉ Customize an HTTP endpoint in Azure Functions - aka.ms/azfr/651/01
◉ Three ways serverless APIs can accelerate enterprise innovation (blog post) - aka.ms/azfr/651/02
◉ Azure Functions - aka.ms/azfr/651/03
◉ Build Serverless APIs with Azure Functions - aka.ms/azfr/651/04
◉ Create a free account (Azure) - aka.ms/azfr/651/free
#Microsoft #Azure - Věda a technologie
Serverless == Less Servers - love that!
Thanks in a million Jeff & Scott. Awesome stuff. Second to NONE
It's awesome how Azure functions can easily scale up
This is awesome. I'm still going to need a little help to migrate the site and will have to make calculations for the actual cost for the whole year. Good Start. Thank You Scott.
Serverless == Server (Management) Less. There are no serverless but the management. Awesome things. Thank you very much for sharing this! Love it...
This is a good workflow that can cleanly integrate Azure Functions.
I love it ,you guys are awesome,thanks a lot ,a lot to go,miles to go ...
Awesome content, thanks :)
I love Azure Functions.
Scott.. You are Awesome.. You are the STAR! what if you are Constellation! :D
Very interesting 🔥 I was planning to move our existing node js api written in loopback framework from app service to function app, but I can't without some code refactoring. Is there any way to overcome this challenge?
Is there a way to implement exception filter or exception Middleware in azure functions with Net5. I'm not able to find httpcontext objects to form the response based on different exception. If any advice is there, kindly share
Problem with consumption plan is that it can't use Managed Identity and Service Bus triggers.
Too many hidden limitations with consumption plans yes. End up with the P plans at 60 per month min.
@Scott, in your text you mentioned that you were using same app service plan to run Azure Function as that of the one hosting your web-site. I am not able to understand the downside of it ? Will it not save me some cost ?
Networking and vnet limitations here which aren’t clear, typical azure, looks great but in a business with a strong security team, it will force you to configure things which require separate plans or grouping of apps to plans.
Aws lambda can do aspcore apps as serverless can’t they? MS a bit behind here. You constantly saying….. in aspcore I do this, how do I do that in a function which don’t really want you doing it.
Not the greatest of ideas to have code in __init__.py file, you can, but not ideal as that file is meant to define a package, any code would have to be for that specific purpose. Not sure many devs expect to have code there.
It’s the azure template default. No point in changing the entry point if your code is pretty minimal. I keep this simple and push other code into packages.
When Azure beats up non Azure parts of your architecture by being way more scalable, and then looks after them too....
#Azure #accenture #ambg