Azure supports two types of queue mechanisms: Storage queues and Service Bus queues.Storage queues, which are part of the Azure storage infrastructure, feature a simple REST-based GET/PUT/PEEK interface, providing reliable, persistent messaging within and between services.Service Bus queues are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe, and more advanced integration patterns. For more information about Service Bus queues/topics/subscriptions, see the overview of Service Bus.you should consider using Storage queues when:Your application must store over 80 GB of messages in a queue. Your application wants to track progress for processing a message inside of the queue. This is useful if the worker processing a message crashes
Azure functions are serverless functions. You can build the Azure Function in various languages like Node.js, C#, F#, Python, PHP, and even Java. Azure Fuctions are event driven which will run based on events or triggers. Also azure functions can be testable without publishing it.For Example:- I have a Twitter Account and when some tweet me then azure functions will automatically trigger an email to my mail id.
Follow these links for more detail,
https://dzone.com/articles/when-to-use-logic-apps-and-azure-functions
Thanks
if you dont worry about platform or infra.if you want to avoid cost, because Azure provide build in services these are plug and play no need to develop these things, like azure monitoring, exception handling, monitoringif u go for microservice based archetecture then Azure is very managed plateformif u want to automate your work then go to Azure, rather then giving 24*7 support of an applicationdisaster recovery , replication, cdn etc use As PAASPay As you GO is the plus point.
https://docs.microsoft.com/en-us/dotnet/architecture/serverless/serverless-business-scenarios