Timeline for When is it better to offload work to the RDBMS rather than to do it in code?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2011 at 1:31 | history | edited | JeffO | CC BY-SA 3.0 | added 79 characters in body |
| Dec 19, 2011 at 1:30 | comment | added | JeffO | @Peter Boughton - The question is when is it better to off load to the database. A more powerful database is a reason to consider it. I didn't realize we were only addressing the question to this specific case. | |
| Dec 28, 2010 at 19:07 | comment | added | Jé Queue | @Peter Boughton, DB and app in the same server have order of magnitude less time for interface connection and magnitudes greater IO throughout, there are real reasons to locate these two together. | |
| Nov 16, 2010 at 18:21 | comment | added | GeminiDomino | Hrm. Not sure then. | |
| Nov 16, 2010 at 17:52 | comment | added | Peter Boughton | A LAMP setup is no reason not to have a standalone database server, and nor is a standalone database server a guarantee of more resources nor not being able to change this. | |
| Nov 16, 2010 at 17:40 | comment | added | GeminiDomino | I think Jeff might be talking about standalone Database servers. I probably should have specified that I work mostly on LA[MP]P setups. | |
| Nov 16, 2010 at 17:35 | comment | added | Peter Boughton | "The database hardware has significantly more resources than other servers and you can't change this." -- eh? Where did those two statements come from? | |
| Nov 16, 2010 at 17:27 | history | answered | JeffO | CC BY-SA 2.5 |