The key is to reduce the overhead for processing a query. Whether or not the final persistent storage is a RDBMS or not is irrelevant - the primary storage should be a RAM-store of some sort. It could flush to a RDBMS any changes on a regular basis, say between requests. Doesn't matter much.
The point is that talexb's problem arises out of two issues:
- The overhead of RDBMS requests
- The need to have a traffic cop
I feel that my design would provide a lightweight solution that provides for both issues.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
| [reply] |