Timeline for When is the point where a JSON text file storage is not enough?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| May 3, 2019 at 20:12 | comment | added | amon | “starting out, JSON is simply the easier solution” – but thanks to embedded databases like SQLite not by much. IMO it's reasonable to say that choosing SQL from the start might be a good idea if it is feasible that the needs could grow beyond file-based storage. | |
| May 3, 2019 at 11:48 | comment | added | R. Schmitz | @jonrsharpe Both perspectives are valid. I just wanted to make the point that switching right now being better does not mean that switching gets prioritized over fixing bugs or adding features. Like I said in the last sentence, they might still be using JSON even though every engineer has been saying they should switch over to SQL since 3 years. | |
| May 3, 2019 at 11:39 | comment | added | jonrsharpe |
Isn't the progression SQL < JSON, SQL > JSON but SQL - switching effort < JSON, SQL - switching effort > JSON? The contemporaneous business needs are implicitly part of the comparison.
|
|
| May 3, 2019 at 10:59 | history | answered | R. Schmitz | CC BY-SA 4.0 |