I'm not sure it is a bad idea so much as not the one size fits all solution. It's fast, easy administratively to setup, works on Heroku with no addons, and gre

I'm not sure it is a bad idea so much as not the one size fits all solution. It's fast, easy administratively to setup, works on Heroku with no addons, and greatly reduced the gap between data entering our system and data being indexed for search results (an important consideration for our problem). It's not perfect, but it is a definite improvement over our previous separate db + ft engine solution.