AWS Lambda presents a base image ready to be provisioned as multiple instances.
If you are familiar with Docker you can think about Lambda image as a small Docker image, while real work will be done in instances (Docker containers) created from this image.
Usual scenario is to provide ready to go image (with all source code, npm packages being installed, with Chrome Headless plugin, etc). Then AWS/Azure will run VM instances based on the image for almost every function request. Most of the time spinning such lite VMs takes no more than a couple of seconds.
1) Event Grid is similar to Amazon SNS => push messages to many kind of subscribers. EG guarantees delivery of a message on the transport level. What is going in case of the failure calls after resending attempts (dead queue or something)?
2) EG is a very different beast in comparison to Azure Event Bus. EG is the magical connector for different endpoints, while AEB is the robust storage of events + limited publisher. Is it correct?
If you are familiar with Docker you can think about Lambda image as a small Docker image, while real work will be done in instances (Docker containers) created from this image.
Usual scenario is to provide ready to go image (with all source code, npm packages being installed, with Chrome Headless plugin, etc). Then AWS/Azure will run VM instances based on the image for almost every function request. Most of the time spinning such lite VMs takes no more than a couple of seconds.