Question 120359 in Firebase Question posted in
An extensive official documentation can be found here.

Firebase – Using a search engine (like Algolia or Typesense) as a primary data source

I have been developing apps that use Firestore as a primary data store and Typesense for full-text search. Some collections are completely duplicated and synced between the databases.

Is there a reason why I should not use Typesense as the SOLE data collection and avoid keeping a collection of the data in Firestore?

What are the downsides of using a search engine as a primary datastore? Expense? Scalability?

Tags:

2

Answers


  1. 0

    Is there a reason why I should not use Typesense as the SOLE data collection and avoid keeping a collection of the data in Firestore?

    Security, scalability, offline data persistence, and interoperability with all the other Firebase products. Besides that, I think that the following resource might also help:

    Login or Signup to reply.
  2. 0

    That depend of your business and your process to input datas in your system.

    If you need a specific backend, firebase cloud-function coupled with algolia, is a good option. with npm algoliasearch

    As database with firebase no cost, (only read and write does),so is not a big deal to keep data in Firebase and perform search engine and filters UI with algolia

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search