On 2022-03-17 3:41 PM, Dave wrote:
I’m a big believer in the right tool for the job. Like what said before if you’re doing just a field:value query or four and no complications, sure use a standard rdbms. But if you inform the client that something like Leaves And whitm* title^3 with bf:title^3 author ^2 Is possible, the conversation changes with the right questions.
Scale also matters. A "one huge text field" in postgres will work well enough given infinite RAM and CPU cycles. We actually tried that once, and ended up dumping that into redis instead: even for our fairly small database the wall clock time from button click to search results page wasn't great.
Dima
