Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wdb:developers:future_work [2008-12-10 10:45:40] michaeloa |
wdb:developers:future_work [2022-05-31 09:29:32] (current) |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Scaling Hardware Vertically ===== | ===== Scaling Hardware Vertically ===== | ||
| + | |||
| + | Vertical scaling: essentially adding more hardware ressources to the same machine (i.e., more and faster processors, memory and disk). | ||
| + | |||
| + | * Expensive | ||
| + | * Simple | ||
| + | * Single point of failure | ||
| We must ensure that WDB scales vertically with the hardware; i.e., increasing capacity by upgrading hardware specifications, | We must ensure that WDB scales vertically with the hardware; i.e., increasing capacity by upgrading hardware specifications, | ||
| Line 11: | Line 17: | ||
| ===== Scaling Hardware Horizontally ===== | ===== Scaling Hardware Horizontally ===== | ||
| + | Horizontal scaling: Adding more machines into the mix - usually cheaper, smaller system. | ||
| + | |||
| + | * Cheap(er) | ||
| + | * Hard to implement | ||
| + | * Multiple points of failure | ||
| + | |||
| + | We would like to construct a framework for WDB that scales horizontally on the hardware; i.e., it should be possible to add new servers to our existing infrastructure and have it seamlessly improve performance of reads and (maybe) writes. | ||
| ===== Optimizing WDB ===== | ===== Optimizing WDB ===== | ||