-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Kinto Vs Elasticsearch Vs Hasura #2237
Comments
You can use Kinto with Elasticsearch if you need fulltext search capabilities. We also have a kinto-algolia plugin if you want to use algolia as a fulltext engine. I guess Hasura and more generaly GraphQL have both the same issues Kinto was built to fix: Fined grained permissions on records If all your data are public in your backend and that you don't need authentication then you should take a closer look at Hasura. However if grating access, managing users data or sharing between users is a feature of your application, Kinto might be the tool you are looking for. |
@Natim Thank you so much for your quick reply |
I haven't really looked at Hasura yet. So don't no if this is feasible at all, but maybe there could be also a Kinto plugin for Hasura. Or just a proposal for discussion as a starter. To have the authentication and permission system of Kinto with a GraphQL query system. Modern frontend frameworks, for example based on Gatsby, will easily benefit from that :) |
Having a GraphQL endpoint for Kinto seems like a good idea. Feel free to start a proposal of how you see this work. |
Here mozilla-services/buildhub#128 I find some reasons for using Elasticsearch within Kinto. Also, found comparison http://docs.kinto-storage.org/en/stable/faq.html
If I'm right, Kinto is using PostgreSQL. In that sense, how it is comparable with Hasura? Similarly, what is the benefit of Kinto over Elastisearch? (Apologies if these are addressed somewhere. TIA)
The text was updated successfully, but these errors were encountered: