In this post, we will take a step back, and discuss how could we start small and simple with our website before considering any scalability options, and we will discuss when should we start considering them.
This is the simplest configuration, and the one you may start with for your small business or project.
You need the following parts in your system:
Server in which you will host your website/system, and this server (computer) should be an always-connected server as you need to server your customers (clients) in any time!
- The server could be your personal computer or a cloud-based one!
- Since we have a single server, all of our applications will be installed and served from it. This includes any database management systems (like MySQL, PostgreSQL, or MongoDB), dynamic, and static resources (like images, videos, web-pages, CSS (Cascading Style Sheets) files).
DNS (Domain Name Server) is the server that provide your customers with your IP (Internet Protocol) address.
- This is usually a paid server.
- The simplest abstraction to think about DNS is a system that acts like a cache, or a map to convert your domain name (like www.noor.guru) to an actual IP address (like 188.8.131.52) of the server with your actual website contents.
- Your first time users will connect to the DNS once, and when they got the actual IP of your server they start to send HTTP (Hypertext Transfer Protocol) requests directly to your server.
- You may (or may not) got a static IP address for your server (as it’s an extra paid service), that’s why, once in a while, your users will be connected to the DNS again to make sure that they have the recent IP address of your server (this depends on multiple factors and could be discussed later).
The following figure illustrates the flow that your customers will have once your website is live.
When (and Why) to Use a Single Server Configuration?
This (simple) configuration should be fine for a small personal website, blog, forum, or a small static website. If that’s what you are looking for, don’t look further (unless, of course, you want to learn or work in the field!)
When (and Why) to Scale?
This (simple) configuration cannot take you beyond some simple or basic scenarios. At some point, or for other use-cases from the start, you should consider the possible ways of Scalability .
When this time will come? and when should you consider the different Scalability options? If you have any of the following points or scenarios, then that time is NOW:
Increase in Traffic, as your customers base grow, the load will increase on your single-server resources (such as CPU, Memory, and I/O Operations).
Increase in Data, as your customers base grow, you will have a lot of data to store, process, and serve. Given that the database queries are not the simplest tasks for your CPU and memory, you should really consider to scale at this point!
Concurrency Limits, as your customers base grow, you will have more users connects to your server in the same time, and while your server could server 1000 users 5 by 5 (5 at a time), it may not be able to serve the same 1000 users 20 by 20 (20 at a time)!
System Growth, as your business grow, you may need to add more and more new functionalities to server your customers. You should be aware that this will push your server resources even harder.
As you may notice, all the first 3 scenarios depend on your customer base growth, so expect them to happen simultaneously!
How to Scale?
There are multiple scalability options, and that’s exactly what we will talk about in this series! So stay tuned!