Ok thank you for asking around.
I was hoping to be able to integrate some of the great performance that Weaviate offers into a command line interface tool that I was building for doing vector searches on genomics data on my local machine.
I understand there is a lot going on under the hood and this type of use case will never be supported, but architecturally, I’m curious where in the source code are the higher level server side read, write, delete, search interface functions defined?
Thank you