Is serverless the future of or just a niche for small applications?

All answers to this question.

Serverless is definitely expanding its reach in the <cloud computing> space, but it isn't a silver bullet. For event-driven microservices, it’s unbeatable because you don't pay for idle time. However, for long-running processes or applications requiring low-latency "warm" responses, traditional containers on Fargate or EKS are often better. Cold starts have improved significantly with features like Provisioned Concurrency, but they still exist. The goal of modern <cloud computing> isn't necessarily to go "serverless" but to go "No-Ops," where you minimize the time spent managing the underlying infrastructure regardless of the compute model.

   Answered 2025-11-24 by Deborah Long

Have you considered a hybrid approach where you use <cloud computing> containers for your core logic and serverless for the asynchronous helper tasks?

   Answered 2025-11-26 by Kenneth Moore

• Kenneth, that's what we are leaning towards. We want to keep the API on a steady EKS cluster but use Lambda for image processing and email triggers. My main concern is the complexity of monitoring a split architecture like that. Do you find that distributed tracing tools like X-Ray or Honeycomb handle the transition between containers and serverless functions well enough for debugging?

     Commented 2025-11-27 by Brandon Knight

Serverless can be very expensive at high scale. Once your <cloud computing> workload is consistent, a reserved instance or a container is often cheaper than per-request billing.

   Answered 2025-11-28 by Martha Dixon

• Martha makes an excellent point. Serverless is cheap to start, but the "success tax" is real once you hit millions of executions per day.

     Commented 2025-11-29 by Patrick Sullivan