mirror of
https://github.com/donnemartin/system-design-primer.git
synced 2025-12-18 19:08:57 +03:00
re-arrang follow table content
This commit is contained in:
20
resources/noat.cards/01 Performance vs scalability.md
Normal file
20
resources/noat.cards/01 Performance vs scalability.md
Normal file
@@ -0,0 +1,20 @@
|
||||
+++
|
||||
noatcards = True
|
||||
isdraft = False
|
||||
+++
|
||||
|
||||
# Performance vs scalability
|
||||
|
||||
## Performance vs scalability
|
||||
|
||||
A service is scalable if it results in increased performance in a manner proportional to resources added. Generally, increasing performance means serving more units of work, but it can also be to handle larger units of work, such as when datasets grow.[1](http://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html)
|
||||
|
||||
Another way to look at performance vs scalability:
|
||||
|
||||
- If you have a performance problem, your system is slow for a single user.
|
||||
- If you have a scalability problem, your system is fast for a single user but slow under heavy load.
|
||||
|
||||
## Source(s) and further reading
|
||||
|
||||
- [A word on scalability](http://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html)
|
||||
- [Scalability, availability, stability, patterns](http://www.slideshare.net/jboner/scalability-availability-stability-patterns/)
|
||||
Reference in New Issue
Block a user