I've got a sideproject brewing for which I think the ZODB might be a really good fit, but I'm totally new to it. I read Chris's blog post on it, and my only concern was that he said it's really good for stuff with mostly read access.
I expect this project will be doing a *lot* of writes. IE, maybe even all hits do some minor mutation. On the other hand, I have a hunch that the architecture could wind up being really clean in zodb as it's going to be a lot of object modelling (some non-realtime simulation related stuff) And I think transactions will be important, it will be all screwed up if there's any kind integrity jiggery pokery in the object model. Wondering if anyone can weigh in on: - how is zodb if you're doing a lot writing? - experience using it as a persistence scheme for (slow) simulations - any misc thoughts on zodb thanks Iain -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
