On 2/21/07, Mark Waser <[EMAIL PROTECTED]> wrote:
and I think that there are a whole bunch more of similar cases that add up and add up and add up. Did you have to write code to load and save from memory to disk (both for swapping and semi-permanent purposes)? Are you confident that you know and have all the tricks necessary to scale up that enterprise Dabs already have (effectively for free to you)? And what about concurrency? Is your architecture designed *from the ground up* to allow controlled parallel, simultaneous operation?
Incidentally, for those things (scalable write/search/read of large data sets) which existing database engines do well, which one would you recommend? For example, I remember hearing years ago that MySQL should be avoided other than for read-only operation due to lacking adequate transaction handling, but I've also heard it's improved a great deal in the meantime, is that the case? ----- This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?list_id=303
