{"id":6270,"date":"2018-10-30T08:00:54","date_gmt":"2018-10-30T15:00:54","guid":{"rendered":"http:\/\/softwareengineeringdaily.com\/?p=6270"},"modified":"2018-10-31T07:02:47","modified_gmt":"2018-10-31T14:02:47","slug":"serverless-backend-using-aws-lambda-hands-on-guide","status":"publish","type":"post","link":"https:\/\/softwareengineeringdaily.com\/2018\/10\/30\/serverless-backend-using-aws-lambda-hands-on-guide\/","title":{"rendered":"Serverless Backend using AWS Lambda: Hands-on Guide"},"content":{"rendered":"
\n
\n
\n

This article was originally written by Rajat <\/a>S on Medium<\/a>. Reposted with permission from Bits and Pieces<\/a>.<\/em><\/p>\n

\n

Serverless architecture refers to the concept where you give your backend logic to a third party vendor\u2019s server architecture. Doing this allows a developer to focus more on their app and not worry about the server at much.<\/p>\n

The word\u00a0Serverless\u00a0<\/strong>may misguide one into thinking that there is no server attached to the app. In truth, it just means that the developer does not have to worry about maintaining the backend logic. That responsibility is handed over to the third party vendors like AWS, Azure, and Google.<\/p>\n

Serverless Computing can be divided into two variants:<\/p>\n