The problem with traditional hosting
Let’s say you own a design agency called PixelWixel (not a real company) and you designed and coded your website using WordPress. Now, you need a home for the website so that people can see PixelWixel.com all over the world, any time of the day. That’s where a server comes into the picture, to store the files and database that power your website and display the output (your website) to the world. The companies managing these servers are called hosting companies.
WordPress is considered an application that needs resources from the server in order to run. Traditional servers have a fixed amount resources. Therefore, if PixelWixel becomes wildly popular and people are clamoring to visit the website, there will be a spike in traffic, which requires a lot of server resources, and could cause your website to go down. Some hosting companies offer scaling solutions, but you need to predict traffic spikes and request extra resources ahead of time, and hope that it’s enough.
Serverless Hosting and Architecture: The revolution is here
First of all, the term “serverless” isn’t entirely accurate. With serverless architecture, there are still servers involved but the way that they process your website is radically different. Instead of having fixed resources running all the time, serverless architecture runs when triggered by an event, like a new visitor to the website. With serverless hosting, you don’t need to worry about scaling or traffic spikes, because it is inherently elastic and you’d never need to add more server resources ahead of huge press coverage.
Strattic to the rescue
Srattic publishes sites as serverless so that scaling is no longer an issue, and your site is available all the time. Everywhere.Serverless
Tags: hosting, scalability, serverless