Database search "limitations"
-
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?
-
@tschlegel There are differences between the database search engine and using open search. Some of the searches are more limited with the database search engine.
"If you don’t need advanced searching capabilities, you may be able to use the database search engine for large installations. This is not a use case FusionAuth tests, so ensure you provision your database with enough resources and benchmark your typical use cases."
