Serverless Architecture
What is serverless architecture?
Serverless architecture is a way of building and running applications where the developer writes code and deploys it to the cloud, but never manages the underlying servers. Despite the name, servers still exist — they are simply managed entirely by the cloud provider, invisible to the developer.
Serverless principles are baked into modern headless CMS platforms. When you build a Wix website with a headless CMS, the entire backend infrastructure — scaling, uptime, and server management — is handled for you. The Wix Headless blog explores how teams are using managed infrastructure to ship faster.
How does serverless work?
Traditional web applications run on servers that are always on, waiting for requests. Serverless flips this model. The application is broken into individual functions that are deployed to a cloud provider and executed on demand.
When a request arrives, the cloud provider:
Receives the trigger — an API call, a scheduled event, a file upload
Allocates compute resources automatically
Runs the relevant function
Returns the result
Releases the resources
Benefits of serverless architecture
No server management. Infrastructure provisioning, patching, and scaling are handled entirely by the cloud provider.
Automatic scaling. Serverless functions scale instantly in response to demand.
Pay per use. You are billed for the compute time your functions actually consume.
Faster development. Without infrastructure to manage, developers focus entirely on application logic.
High availability. Cloud providers run serverless functions across multiple data centers.
Serverless vs. traditional hosting
In traditional hosting, you rent server capacity and your application runs continuously. Scaling means provisioning more servers, which takes time and costs money.
Serverless eliminates this overhead. The trade-off is less control over the runtime environment and potential “cold start” latency for infrequently called functions.
Serverless and headless development
In a headless architecture, serverless functions are often used to handle the logic layer between the frontend and backend.
Platforms like Wix Headless abstract the serverless infrastructure entirely. The business logic for eCommerce, bookings, memberships, and payments is managed by Wix, leaving developers free to build their frontend with whichever framework they choose.
Common serverless use cases
API backends — handling requests from a mobile app or web frontend
Data processing — transforming or validating data when a file is uploaded
Scheduled tasks — running reports, sending reminders, or syncing data on a schedule
Event-driven workflows — triggering actions in response to payments, form submissions, or webhooks
Real-time notifications — sending emails or push notifications when specific events occur
Comments