Timeline for All possible ways to Scale a Database
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20 at 4:50 | answer | added | Rick James | timeline score: 0 | |
| Oct 20 at 3:26 | comment | added | Intangible _pg18 | @RickJames Scale for the incoming traffic | |
| Oct 19 at 19:59 | comment | added | Rick James | "Scale" what? Performance? Data size? Number of connections? Something else? | |
| Oct 12 at 20:29 | comment | added | J.D. |
Options E, F, & G are all arbitrary combinations and not a fully complete list. E.g. Partitioning can be used on it's own as well, for specific use cases. And then different RDBMS have more specific technologies that can be used to help with scaling as well. E.g. besides Replication, SQL Server also has Log Shipping and AlwaysOn Availability Groups which can be used for improved horizontal scalability.
|
|
| Oct 12 at 19:33 | comment | added | Frank Heikens | Q4: I got PostgreSQL versions 12 to 17 running on my laptop, ports 54312 up to 54317. | |
| Oct 12 at 19:27 | comment | added | Rick James | Q3: Clumsy. Q4: Doable (eg with Docker), but it is not practical for "scaling". Instead for testing, etc. | |
| Oct 12 at 14:29 | review | Close votes | |||
| Nov 4 at 3:05 | |||||
| Oct 12 at 6:15 | answer | added | Vérace | timeline score: 1 | |
| S Oct 12 at 4:54 | review | First questions | |||
| Oct 12 at 14:13 | |||||
| S Oct 12 at 4:54 | history | asked | Intangible _pg18 | CC BY-SA 4.0 |