Serverless is a very specific model. Pay only for when code actually need to run. Example, some code needs to run all the time, should be on app service.. Some code can run seldom, for example, a new customer signed up. Serverless is more expensive if the code you make serverless runs all the time.. So Serverless is niche case, you should not turn all your code serverless, just code that can run seldom
I am a Full stack .NET Developer, I like to work with C#, Asp.Net Core, SQL, Mongo DB, Azure, JavaScript...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
Serverless is a very specific model. Pay only for when code actually need to run. Example, some code needs to run all the time, should be on app service.. Some code can run seldom, for example, a new customer signed up. Serverless is more expensive if the code you make serverless runs all the time.. So Serverless is niche case, you should not turn all your code serverless, just code that can run seldom
Great use case. Now I understand that all code cant be made serverless. Thank you.