&gt; Of course, it&#x27;s also good at many things like simple filtering and aggregation against &quot;real-time&quot; data.<p>And also fulltext search at scale, which is basically its primary use case.<p>PostgreSQL&#x27;s fulltext search isn&#x27;t quite at the same level. The last time I looked into its capabilities, it didn&#x27;t fully support TF-IDF. (I don&#x27;t think it keeps track of corpus frequencies for terms.) Interestingly, I think SQLite&#x27;s fulltext support does include TF-IDF, but I could be misremembering.<p>I mean, the Elasticsearch docs are pretty clear that joining doesn&#x27;t work well (or really, at all). I&#x27;m not sure how being clear about the trade offs of your software is &quot;doing a disservice.&quot; Sometimes you don&#x27;t need to store relational data. Sometimes you do need to store relational data, but the other benefits of Elasticsearch outweight shoehorning relational data into what is effectively a document database.<p>If your only complaint is that people misuse software... Well... Yeah. It&#x27;s been happening for a while now. We should help educate others. I&#x27;m not sure your approach is the most constructive.