<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Can you use the database search engine with millions of users?]]></title><description><![CDATA[<p dir="auto">Are there any issues with running the database engine only, even if you have millions of users?</p>
<p dir="auto">If you don't need search capabilities and size your db correctly, any reason not to simplify and avoid ES?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/771/can-you-use-the-database-search-engine-with-millions-of-users</link><generator>RSS for Node</generator><lastBuildDate>Wed, 17 Jun 2026 07:44:38 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/771.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 26 Jan 2021 22:43:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Can you use the database search engine with millions of users? on Wed, 27 Jan 2021 01:32:34 GMT]]></title><description><![CDATA[<p dir="auto">I don't know of any issues. You’re mainly just giving up the ability to perform rich queries. The db search is a few <code>LIKE</code> statements.</p>
<p dir="auto">I don't think we've tested millions running db search - but the only issue I can think of for normal usage would be the User page in the UI since we’ll be paginating over lots of users.</p>
<p dir="auto">This should work ok - but pagination tends to slow way down as you get into higher pages,.</p>
<p dir="auto">One can always <a href="https://fusionauth.io/docs/v1/tech/tutorials/switch-search-engines/" rel="nofollow ugc">flip on Elastic and run an index</a>, so not much harm in trying it.</p>
]]></description><link>https://fusionauth.io/community/forum/post/2269</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/2269</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Wed, 27 Jan 2021 01:32:34 GMT</pubDate></item></channel></rss>