Currently trying to differentiate when to use Servers & when to go Serverless. Serverless will scale infinitely, although it has 1 small cost of cold starts but if the site is used regularly then cold start is not needed. Servers are inherently costly. Even if we don't use it to its full potential we need to always choose a higher plan than our current usage. I want to know when can we go full Serverless. Like I have 1 app where the flow is like - 1. User clicks on SignIn 2. Email is sent to the user with Magic Link 3. After Magic Link is clicked, user is logged in 4. User can then buy a product 5. After payment, user can download the product 6. User can Logout Can this be done serverless ? Also, which websites would be Serverless & which would need Servers ?

Hi Akshay, "Serverless will scale infinitely, although it has 1 small cost of cold starts but if the site is used regularly then cold start is not needed." - there are solutions that fix it, example: https://github.com/FidelLimited/serverless-plugin-warmup Me and my teammates have been using serverless technologies for a while. This is what we've learned: 1. Running Lambda functions is much cheaper for simple computationally intensive operations. 2. Traditional way of dealing with databases is not a good fit for serverless. Make sure that your DB server is ready to handle hundreds of simultaneous connections. Always close DB connections by the end of each lambda invocation. 3. Use terraform, cloudformation or serverless.js config to set up API endpoints, don't do it manually (otherwise it is a nightmare to set up staging or other envirionments). 4. Long running tasks (like log processing, etc.) are better to do on a server instance. 5. Lambda functions are great for running CRON jobs (using cloudwatch scheduler). 6. Think of a centralized logging solution in advance (Papertrail is a good option). 7. Ideally set up caching with Redis (has unlimited connections) to reduce the load on your DB or consider trying AWS Aurora: https://aws.amazon.com/rds/aurora/ It's a Postgres compatible solution for the serverless era. Let me know how it goes. You should think carefully of how to implement authentication properly. The best fit would be using a JWT token. Tj has recently introduced Up, which helps to deploy serverless websites as well (not only APIs): https://github.com/apex/up We prefer having a Heroku instance or a static website running on a server and then using serverless for the API, because the limitation is that you can't use Websocket without a server. In general, it's definitely fun and cost efficient to build a cloud solution using serverless technologies. Guys, hit me up on Telegram (@mac_r) if you have any other questions! Best, Max