There's a question I don't find an answer for by looking at homepage and documentation: does it handle concurrent queries? (I wonder, since I see a store is a single file)
That is, is it something akin sqlite, meant to be used as an embedded engine for standalone applications, or is it fit to be used by a centralized api?
Concurrent indexing is also possible, so long as you can arrange to not put duplicate document ids into batches executing concurrently.
As for usage, it is just a library, so it is typically embedded in a single process (though this can serve multiple clients concurrently).
Distributing the index across multiple nodes is done at the application level. At Couchbase we do this with bleve in a separate project called 'cbft'.
I see, my bad. I saw one binary file named "store" in the directory created by the example code, I thought it would be it.
Thanks for explanation!