greenrobot

ObjectBox CTO here...

Note that this is not just running a lib like HNSWlib or FAISS on top of database persistence. It's deeply integrated with database internals, which is also why in runs nicely with low-memory devices. The entire binary is like 3 MB, so leaves lots of resources to actual vector data and LLMs.

AMA...

Interesting. Would you mind to go into details about dropping RAFT? It would make a great tech blog post imho, but maybe you could share some high level insights on that?

Related to that: have you considered extensions to the RAFT standard e.g. pipelining?

PostgreSQL? I'm confused.

SQLite is a very nice embedded DB indeed. If you like SQL. ObjectBox enables you to work with Go structs and gives you additional performance.

The initial question was about Realm, thus the link to Java. The core of ObjectBox is the same on every platform (C/C++ for maximum speed). We haven't finished the other benchmarks yet. Sorry for teasing with those. We'll be done with those soon and they will be open source.

The FAQ covers this: https://golang.objectbox.io/faq#how-is-objectbox-different-f...

Interesting. ObjectBox does NOT use os.File.Sync. This stuff is done by a low-level C layer. We'll verify next week, thank you!

Good old days... :)

You probably don't do a lot of queries? Badger is a K/V store and has no knowledge about the value. Thus querying sucks and if you want indexing, you are on your own. Relations? Anyway, for simple caching that's probably fine.

There's a open source benchmark here: https://github.com/objectbox/objectbox-performance - last time I checked ObjectBox was several times faster than Realm.

Not sure if Versant supports Go. Anybody knows Versant's pricing? Don't think they come for free.

Do you refer to https://golang.objectbox.io ? Check https://docs.objectbox.io/ for what is available for Java.

It's ACID compliant, and thus not not in-memory. https://golang.objectbox.io/faq covers that in detail. In the FAQ, there is a section on comparing to JSON; I guess the same would hold true for CSV.

PS.: Wouldn't worry about a label saying "IoT" if the technology fits your need.

The Go release post (https://objectbox.io/go-objectbox-golang/) has some numbers. "On a i7-8850H CPU, ObjectBox consistently processes over 1.5 million CRUD operations per second with 4.4 million object reads per second."

Not really, ObjectBox is an object DB and emphasizes performance (no JSON but FlatBuffers for example).

Yeah, me too.

ObjectBox DB | iOS and C++ developers | Full time | ONSITE and REMOTE | Munich, Germany

ObjectBox (Techstars ’17) is a well funded startup that helps app/IoT developers develop faster apps faster by ensuring data is where it is needed when it is needed. The core of this solution is our embedded mobile database which is 10x faster than SQLite. On top of the database, we’re building a data synchronization solution. We are also the team behind the open source projects, which are used by 30% of the top-500 apps on Google Play.

• iOS dev: Using ObjectiveC/C++ and Swift, you will build the iOS API for ObjectBox. http://objectbox.io/jobs/ios-objective-c-developer/

• C++ dev: Work on ObjectBox' core and data synchronization. http://objectbox.io/jobs/objectbox-senior-c-plusplus-develop...

Speed: Check https://github.com/objectbox/objectbox-performance open source project or https://www.netguru.co/codestories/realm-vs-objectbox-compar... for independent evaluation.

FAQ: What's different to Realm? Simpler to use with POJOs, no threading constraints. Relations can be eagerly loaded to prepare everything in the background.