Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

When not serverless

This revision card explains When not serverless. It starts from the need that forcing every workload into Lambda creates painful workarounds. It describes long jobs, sticky sockets, always-on low latency , then ECS/EC2/Batch. The how-to section notes list job length , then stateful needs , then pick Lambda or container. An example on the card is arjun Mehta moves 90-min encodes off Lambda on day one.

When not serverless Forcing every workload into Lambda creates painful workarounds. Long jobs, sticky sockets, always-on low latency → ECS/EC2/Batch. List job length → stateful needs → pick Lambda or container. Arjun Mehta moves 90-min encodes off Lambda on day one.
When not serverless · Download PNG
Read card text

What this card says

Why do we need it?

Forcing every workload into Lambda creates painful workarounds.

What is it?

Long jobs, sticky sockets, always-on low latency → ECS/EC2/Batch.

15 minutes

How to do it

List job length → stateful needs → pick Lambda or container.

Example

Arjun Mehta moves 90-min encodes off Lambda on day one.

See all AWS revision cards