Comparing Firebase and Typesense Pricing and Performance
TLDR Andrew inquired about the cost-effectiveness of Typesense versus Firebase. Kishore Nallan confirmed Typesense's lower pricing but noted its less resilience compared to Firebase.
1
Nov 23, 2022 (13 months ago)
Andrew
06:16 AMAm i thinking about this correctly? Id like to read the majority of my data from typesense if so, for the above reason along with TS having better querying capabilities.
Kishore Nallan
06:20 AMā¢ There is also a bandwidth component for the pricing, but this is typically not a problem for most use cases.
ā¢ A single Typesense instance is probably not as resilient as Firestore in an apples to apples pricing comparison (for e.g. if the host goes down it will take some time before it comes back up). The HA configuration is recommended if you want greater guarantee there, which will require running a 3-node configuration.
1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
High Cost Concerns with firestore-typesense-search Extension
Minyong is confused by the high costs of using the firestore-typesense-search extension and asks for ways to reduce them. Jason confirms that the extension does not batch requests and advises Minyong to consult Firebase support.
Understanding Typesense Cloud Pricing and Bandwidth Costs
Ripas55 seeks clarity on Typesense cloud pricing and bandwidth costs. Kishore Nallan explains the pricing as per node configuration and bandwidth out consumed costs, elaborating that the later is not typically a significant expense.
Discussing High Bandwidth Usage and Pricing in Typesense
Rude was concerned about their high bandwidth usage due to sharing all fields from firestore documents. Jason confirmed this contributes to their bandwidth pricing.