Prompt
I need a serverless backend for HTTP requests, queues, and cron jobs, what should I choose?
Latest observation
Oct 25, 2026
OpenAI APIWeb search: off
If you want serverless for HTTP requests, queues, and cron jobs, the best choice depends on your cloud preference, but here are the most practical options:
Best overall choices
1) AWS Lambda + API Gateway + SQS + EventBridge
Best if you want a mature, scalable, fully managed setup.
- HTTP requests: API Gateway → Lambda
- Queues: SQS → Lambda
- Cron jobs: EventBridge Scheduler / EventBridge rules → Lambda
Pros
- Very mature and widely supported
- Easy to scale
- Good ecosystem for serverless architectures
- Works well for small to large systems
Cons
- Can get a bit complex
- Costs can become less obvious at scale
- Cold starts can matter depending on runtime
2) Google Cloud Functions / Cloud Run + Pub/Sub + Cloud Scheduler
Best if you prefer GCP or want more flexibility with containers.
- HTTP requests: Cloud Functions or Cloud Run
- Queues: Pub/Sub
- Cron jobs: Cloud Scheduler
Pros
- Cloud Run is great if you want serverless containers
- Very flexible
- Good integration with GCP services
Cons
- Slightly different mental model depending on service choice
- Pub/Sub is not a classic queue in the same way as SQS
3) Azure Functions + Service Bus + Timer Triggers
Best if you’re already on Azure.
- HTTP requests: Azure Functions HTTP triggers
- Queues: Service Bus or Storage Queues
- Cron jobs: Timer triggers
Pros
- Good if you’re in the Microsoft ecosystem
- Strong enterprise integrations
Cons
- Can be more opinionated
- Some Azure serverless setups are less straightforward than AWS
If you want the simplest recommendation
- Choose AWS Lambda if you want the most proven general-purpose serverless backend.
- Choose Cloud Run if you want serverless but with container flexibility.
- Choose Azure Functions if your stack is already on Azure.
My recommendation by use case
- Startup / general-purpose app: AWS Lambda + SQS + EventBridge
- Container-based app: GCP Cloud Run + Pub/Sub + Cloud Scheduler
- Microsoft shop: Azure Functions + Service Bus + Timer
If you want, I can also suggest:
- the cheapest option,
- the easiest to develop locally, or
- a complete reference architecture for one of these clouds.