> is it actually pausing the capybara/rspec test such that I can have a breakpoint/debugger/REPL experience to try out various capybara/rspec code
That's a good idea. The actual method of pausing is with a ruby Queue#pop within the same thread that the actual ruby test source code is running in. I'm not sure the exact mechanism, but I assume you could run a binding.pry instead, as long as you can "cancel" it from another thread.
Multi-tenancy: I assume you mean organizations w/ user-roles, which we do support
Benchmarks: this is a big one! We have some initial data that shows we’re comparable to elastic for fuzzy-search at medium scale. However, one of our value-propositions is out-of-the-box semantic search, so we’re working on a blog post with the full benchmarking story.
I’m very open to the idea of an on-prem version of Searchbase as an option in the future! We decided to start with a cloud version for our MVP to enable users to get started with Searchbase in a few minutes.
As for sharing DB credentials, I get the concern. “Subscribing” to your database is meant for developer convenience. But if there’s demand, we’d also like to support the traditional ETL method of “manually bulk uploading” :)
Right now a Searchbase api key has read access to an entire index or to an “alias”, which is a filtered subset of an index. I agree that row-level security could be really interesting… Could you give an example of your use-case?
That's a good idea. The actual method of pausing is with a ruby Queue#pop within the same thread that the actual ruby test source code is running in. I'm not sure the exact mechanism, but I assume you could run a binding.pry instead, as long as you can "cancel" it from another thread.