Timeline for Best approach to write on a database with two webservers
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 26, 2016 at 0:57 | comment | added | HorusKol | It is a bizarre hypothetical... Kindif like saying "imagine I can't replace the old tape drive with a new hard disk, how do I manage concurrent random access to storage" | |
| Jun 25, 2016 at 18:23 | comment | added | Brandon | Ok, so it's a hypothetical? I am used to helping solve specific problems on this forum. Point taken. If the question is to suggest how to serialize the inserts without changing the DB, then everybody else's answers have good solutions. This feels more and more like a job interview question. | |
| Jun 25, 2016 at 18:05 | comment | added | Fabio Cardoso | You missed the real point, it's a generic problem with the premise: "without changing the underlying database". I know it's really hard to accept a database that only handles 1 write concurrently. If I could change the DB the whole problem not would be a problem. Thank you anyway for your explanation, it's usefull. | |
| Jun 25, 2016 at 17:45 | history | answered | Brandon | CC BY-SA 3.0 |