/Glossary · Architecture
What is Serverless?
Serverless is a cloud computing model in which the provider manages servers, scaling and availability, and you pay only for actual usage. It lets you focus on code and business logic instead of infrastructure.
How a serverless architecture works
A serverless architecture combines managed services that scale on their own and do not charge for idle capacity. On AWS, the usual setup is API Gateway to expose APIs, Lambda for the logic, DynamoDB or Aurora Serverless for data, S3 for files, SQS and EventBridge for decoupling, and Step Functions to orchestrate processes.
Components talk to each other through events instead of calling each other directly: a file uploaded to S3 triggers processing, a new order publishes an event to EventBridge, and several consumers react independently. That decoupling lets you evolve each part without coordinating massive deployments.
When serverless makes sense
It fits new products that need to ship fast, workloads with variable or unpredictable traffic, system integrations and event processing. It also fits small teams that do not want to spend time on OS patching, cluster scaling or idle capacity.
It may not be the best option for very high, steady traffic, long-running processes or software dependencies that need a controlled runtime environment. In those cases, containers on ECS with Fargate keep much of the operational simplicity with a more predictable cost model.
Best practices and common mistakes on AWS
Design for idempotency and dead-letter queues, define infrastructure with AWS SAM, CDK or Terraform, and use distributed tracing to follow an event across services. Review the AWS Well-Architected Serverless Lens to validate security, reliability and cost decisions.
Common mistakes: building a distributed monolith out of functions that call each other in a chain, not planning for concurrency limits that overwhelm relational databases, and losing visibility because every component logs in isolation. Another one is assuming serverless is always cheaper without measuring cost against real traffic.
/FAQ
Questions about Serverless
Another question? Write to hello@nubent.com and an engineer will answer.
Does serverless mean there are no servers?
No. The servers exist, but the provider manages them. You do not provision, patch or scale machines: you define functions, tables or queues, and the service handles capacity, availability and scaling based on demand.
Is serverless cheaper than running servers?
It usually is with low or variable traffic, because you do not pay for idle capacity. With high, steady traffic, containers or instances with usage commitments can come out cheaper. Model the cost with your real volume before you decide.
Which AWS services are serverless?
The most widely used include AWS Lambda, Amazon API Gateway, Amazon DynamoDB, Amazon S3, Amazon SQS, Amazon SNS, Amazon EventBridge, AWS Step Functions, AWS Fargate and Aurora Serverless v2. All of them scale without you managing servers.
How we help with Serverless
Serverless on AWS
Lambda, API Gateway, Step Functions, EventBridge, DynamoDB and SQS: event-driven architectures that scale on their own, tolerate failures and bill only for real usage.
Learn moreAWS Application Development
Backends, APIs, frontends on CloudFront and Amplify, databases and CI/CD: cloud-native software built on AWS and ready to run in production.
Learn moreCloud modernization
AWS application modernization: from mutable servers and monoliths to containers, serverless and managed services, in stages and without stalling the product.
Learn moreNext step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.