When building a software infrastructure, it’s important to consider how your code will scale. You want to make sure that your infrastructure can handle large amounts of traffic and data, and that it is built with the right tools for the job.
The Level of Service
When you’re looking at a system’s scalability, the first thing to consider is how many users it can support. This is called “the level of service,” and it’s not the same as performance or security–though those things are important too!
The level of service is an important metric because it directly affects how many people can use your site at once: if too many people try to access your site at once, then some users will get errors or have trouble accessing content (it’s called “denial of service”).
Security is a priority.
It’s not just about technical issues, but also people and process.
Security means different things to different people. For example:
- Software engineers may focus on implementing secure programming practices (e.g., avoiding buffer overruns).
- System administrators may focus on the physical infrastructure of your network and servers (e.g., locking down firewalls).
- Product managers might think about how you can build in security features into your product that make it easier for users who aren’t experts at using encryption tools like PGP email clients or Tor browser extensions for their daily web browsing needs
Performance is about the speed with which your application responds to requests, processes a request and consumes resources.…The Scalability Pyramid Read More