Really great informations :
Scenario���s
In different situations, there are different
storage needs
- You are writing a small demonstration program
to show your customers, and want to populate the system with some
representative data. Add a class instance variable to store the
instances, and simply save the image.
- You have a small system
with a few hundred/thousand objects, and are not dependent on external
systems. A prevayler-like system like SandstoneDB might be a perfect
fit. Each object save means a disk access, so scaling ends with disk
speed. A few old versions of the data are kept around, so backing up or
reverting is easy. If you want a readable representation, SIXX might
help.
- You have a legacy (relational) database, with extensive
reporting written for it. Use an ORM.
- You have a complex and
large object model that has to support changing the object model while
developing. The solution is an OODB. Gemstone is the large and proven
commercial offering. It has a free version for smaller databases (4GB
data, 1 core, 1G ram), and has proven scalability to 500 machines. Magma
is an open source OODB, seeing active development and growing more and
more advanced functionality.
Laurent Laffont
On Wed, Feb 17, 2010 at 3:07 PM, laurent laffont
<laurent.laffont@gmail.com> wrote:
No :)�� Thanks for the link !
Laurent Laffont