Serverless Computing Introduction

In general; Serverless computing is nothing more than a way of running your program in a way that it starts and ends after performing a certain operation.That’s exactly the definition of the main function exists in any popular programming language.

So why we call it Serverless? Does it mean it doesn’t need any server?
The answer is YES and NO, Basically any program needs a machine to run it, So is the Serverless(The “YES” part) but it doesn’t need an ever running machine, Serverless application only needs the machine when it’s running the program, when the run finished the machine is free again and no longer occupied with your Serverless application(The “No” part).
That’s The difference between ever running container based servers and Serverless applications, The ever running server is like 90th robots which were working all the time in the factory while the serverless application is like a robot with a feeling which can sometimes take a rest and go to a beach for a suntan and Pina colada!

Cost Benefits

So what does it mean for you as a serverless user? It means you pay for the server and resources when ever your application is running based on your application load.
Let’s say you have an api server and you want to run it on a Linux server, So, You need to consider the amount of resources such as CPU and Memory you want to use for your application and you should consider the upper bound to handle peak times traffic and those resources are occupied for your api server which means you need to pay for them whether or not there is that much load on your application which needs those amount of resources but in Serverless you only pay for what you use, you may pay more when your application gets more request and much less when it only gets a few.

That was a simple introduction to Serverless computing, I’ll talk more about other aspects of Serverless Such as how it Scales, Serverless Providers, Sample Serverless application and …
Follow me to not to miss any of those! :)))