# Indexer question to Nextant **URL:** \ **Category:** ℹ️ Support\ **Tags:** fulltextsearch-app\ **Created:** [January 9, 2017, 8:26pm UTC](https://help.nextcloud.com/t/indexer-question-to-nextant/7324 "2017-01-09T20:26:26Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Stuart\_Naylor](https://help.nextcloud.com/user_avatar/help.nextcloud.com/stuart_naylor/32/2359_2.png) [@Stuart\_Naylor](https://help.nextcloud.com/u/Stuart_Naylor)\ **Post date:** [January 10, 2017, 12:35pm UTC](https://help.nextcloud.com/t/indexer-question-to-nextant/7324/3 "2017-01-10T12:35:41Z")
Yeah that is one of the things I have been thinking about. Solr can use external storage and the current manner of employment is going to cause obvious problems especially embedded applications. I think its brilliant someone is bring Solr to NC but wow there is quite a bit to think about. > [@Utilizing MySQL fulltext index](https://help.nextcloud.com/t/utilizing-mysql-fulltext-index/7175/2): > > ? That would as its a database query and that side of solr is fast anyway. The slow bit is indexing the documents and that isn’t in your query. I think Solr is definately the way to go as also it fits Nextclouds federated mode. A single line can use the local shard to make a distributed search across many installs in a simple command line. curl 'http://localhost:8983/solr/select?shards=localhost:8983/solr,x.x.x.ip:7574/solr&indent=true&q=ipod+solr' The only dev work by next cloud would be a… --- _[View the full topic](https://help.nextcloud.com/t/indexer-question-to-nextant/7324)._