FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    Database search "limitations"

    Scheduled Pinned Locked Moved Unsolved
    Q&A
    1
    1
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tschlegel
      last edited by

      For cost reasons (etc.) we may not want to run dedicated OpenSearch instances in all of our deployed environments. I see in the documentation that

      The database search engine is appropriate for systems that are not dependent on the FusionAuth APIs, are not expected to have a large number of search results, or are running in an embedded environment.

      I get the performance implications. What i'm curious about is

      The database search engine is appropriate for systems that are not dependent on the FusionAuth APIs...

      Are there API endpoints that don't work without OpenSearch?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post