What do you do after AWS Lambda stops being the right fit?

I like Lambda for a lot of things, but there’s a very specific point where it stops feeling elegant.

Usually it starts with something like:

• a job that runs too long

• a workflow that should keep going in the background

• a task that needs better isolation or custom runtime behavior

• a system that starts needing cron, retries, webhooks, logs, and routing in one place

And then the answer often becomes: move to Fargate, ECS, Step Functions, EC2, or stitch multiple services together.

That works, but it also feels like a complexity cliff.

I’m building Inquir, partly because I kept seeing this transition happen too early. A lot of teams don’t actually want “more AWS primitives.” They want a simpler way to run background work and longer-lived jobs without rebuilding half the platform around them.

For those of you who hit Lambda’s limits in real projects:

• where did you go next?

• Fargate?

• ECS services?

• Step Functions?

• custom worker fleet?

• something else?

Interested in the practical tradeoffs, especially from people who had to support this in production.