The main problem with DB4o is this: can you reduce your network of objects in some useful way? If not, then you will store too many objects in RAM for too long, and your performance will suffer.
For example, in SQL, you can create a cursor and then easily go through a huge set of results. You can also request a small set of columns, while DB4o always loads all objects (and its links and link links). With DB4o, you must make sure that DB4o is not trying to pull all objects from the database at the same time.
You will also need to get used to the queries of things in your "DB" by filling out examples of objects that seem strange at first.
source
share