Hi ,
we are waiting for objectdb 3.0
We expect to see vector db inside objectdb 3.0
like objectbox but with higher storage rates
https://github.com/objectbox/objectbox-java
Do you have any new plans for objectdb 3.0 ?
Hi ,
we are waiting for objectdb 3.0
We expect to see vector db inside objectdb 3.0
like objectbox but with higher storage rates
https://github.com/objectbox/objectbox-java
Do you have any new plans for objectdb 3.0 ?
Hi,
Thank you for your interest. We are working on ObjectDB 3.0, and vector-related capabilities are part of our longer-term plans.
At this stage, we are not in a position to share a specific timeline. We will share more details as they become available.
Regards,
All dbs on market have already added vector capability.
objectbox is very similar and more friendly view with objectdb.
When will you release objectdb 3.0 ?
Any date ?
As mentioned above, we aren't able to share a specific timeline at this point, but we will share more details as they become available.
Every DBMS has its own set of features, strengths, and trade-offs. If another product better fits your requirements, you are free to migrate. Switching is particularly straightforward if the target system supports JPA (and manageable with AI assistance if it doesn't). However, please note that this forum is intended for ObjectDB support rather than promoting alternative products.
That said, we internally use ObjectDB as a lightweight vector database by storing vectors directly in entity objects and loading them into memory. Although it doesn't use vector indexing, it performs well for smaller datasets (e.g., under 1,000,000 documents). In our setup, a query vector is compared against all stored documents sequentially, which provides exact precision at the cost of speed. By using binary vectors (one bit per dimension), each comparison is computationally lightweight, keeping performance fast for moderate document volumes.