Server Backends (Server+)

as the name says they have server and we maintain them O_o,

ik ik its a pain in a** fr

cz of maintainance charges and overheads to maintaina and satisfy all the infra and

‘A C I D’ props of data been stored and retrieved to. yea :

<aside> 💡 When you have to deploy it on the internet, there are a few ways -

1. Go to aws, GCP, Azure, Cloudflare
   1. Rent a VM (Virtual Machine) and deploy your app
   2. Put it in an Auto scaling group
   3. Deploy it in a Kubernetes cluster </aside>

so we have our hero fr the decade -

SERVERLESS BACKENDS

"Serverless" is a backend deployment in which the cloud provider dynamically manages the allocation and provisioning of servers. The term "serverless" doesn't mean there are no servers involved. Instead, it means that developers and operators do not have to worry about the servers.

<aside> 💡

What if you could just write your express routes and run a command. The app would automatically

1. Deploy
2. Autoscale
3. Charge you on a per request basis (rather than you paying for VMs)

</aside>

Problems with this approach

1. More expensive at scale
2. Cold start problem

Cold Start pblm :

Basically these CSPs (cloud service providers) wont make the “servers upp and running for us “

i.e, they’ll start servers/services as and when a user starts using our WebApps , so there will be a latency of 2secs or of something similar duration

“our servers would be in a cold state until there exists a user to”