Replies: 1 comment
-
Thank you for your feedback, @UtfCube! Ease of use is our key priority. It drives all our decisions, e.g., creating super easy-to-use secondary indexes that are just on by default, without the need to configure anything, etc. I agree, though, that there are many aspects that require further simplification. Our Kubernetes support is now limited by the Helm chart, but we are making some progress with it too. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I appreciate the speed of operation and SQL query language support. My experience varies between delight and utter confusion. Overall, the emotions are positive and it seems we have gotten used to the nuances. But if you plan to compete with Elasticsearch, you need to move towards ease of use, so that as many entry-level specialists as possible can easily and comfortably start using Manticore as if it's MySQL. And Kubernetes, without it you won't be able to fully unleash the potential of the database and attract serious specialists with serious projects to switch to your product. Overall, I rate it 7 out of 10.
I also want to express huge gratitude to the whole team, and especially the developers who answer questions in the chat. This really encourages me to continue using your product.
Additionally, I would like to note the promptness and responsiveness when fixing issues. Your team does a great job of trying to close crashes as soon as possible, which also encourages me to continue using the product because there is confidence that the project won't die tomorrow or in a month or in a year.
I wish you and your team success, and we will continue to try to use Manticore in our Kubernetes production.
Andrey Kholzakov,
Lead backend developer on node.js. Company aemedia https://aemedia.ee/ru
Beta Was this translation helpful? Give feedback.
All reactions