Timeline for Best approach for storing huge data
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2015 at 21:09 | vote | accept | JustACPPFan | ||
| Dec 20, 2014 at 21:53 | comment | added | JustACPPFan | @kevinsky: at least 100k concurrent. Yes, I'll be using Amazon cloud so I can add/remove services/servers needed as users growing | |
| Dec 20, 2014 at 21:52 | comment | added | JustACPPFan | @JimG. I should've said minimum. | |
| Dec 11, 2014 at 17:04 | comment | added | kevinskio | How many concurrent users at once? Do you have a hardware budget? | |
| Dec 11, 2014 at 8:28 | answer | added | Jules | timeline score: 1 | |
| Dec 11, 2014 at 7:29 | answer | added | MvdD | timeline score: 0 | |
| Dec 11, 2014 at 6:38 | history | tweeted | twitter.com/#!/StackProgrammer/status/542931305319915520 | ||
| Dec 11, 2014 at 5:47 | comment | added | Jim G. | 300,000 users = Huge Data? | |
| Dec 11, 2014 at 4:38 | answer | added | GrandmasterB | timeline score: 2 | |
| Dec 11, 2014 at 3:19 | comment | added | 9000 | In short: create a single logical table, partition it by whatever you see fit. Usually dates are a better fit than names: old partitions are rarely touched. | |
| Dec 11, 2014 at 3:01 | history | edited | user40980 | CC BY-SA 3.0 |
Format numbered list and code block
|
| Dec 11, 2014 at 1:01 | review | First posts | |||
| Dec 11, 2014 at 5:59 | |||||
| Dec 11, 2014 at 0:59 | history | asked | JustACPPFan | CC BY-SA 3.0 |