Skip to content
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

[PROPOSAL] Use with golang Elastic Search equivalent #82

Closed
gedw99 opened this issue Jan 5, 2022 · 4 comments
Closed

[PROPOSAL] Use with golang Elastic Search equivalent #82

gedw99 opened this issue Jan 5, 2022 · 4 comments

Comments

@gedw99
Copy link

gedw99 commented Jan 5, 2022

** What kind of business use case are you trying to solve? What are your requirements?

Need golang server to have more control over our destiny and hate the JVM ( sorry )

What is the problem? What is preventing you from meeting the requirements?

We are golang coders in the team and so using a golang server is much easier.

What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?

THIS: https://github.com/prabhatsharma/zinc

Its taking off. Does not have clustering yet
but there is another clustered one here https://github.com/mosuka/phalanx, but it needs the ziny APi on top of it.

What are your assumptions or prerequisites?

Dont think i am assuming much. but i probably dont know what i dont know.

What are remaining open questions?

i would like to know if this interests the community.
I can put time into it, but it would be nice to know if others like this idea and is they also want to get involved.

@dblock
Copy link
Member

dblock commented Jan 5, 2022

If Zinc has a 100% compatible API with ES/OpenSearch, then this client should "just work". Have you tried it?

@gedw99
Copy link
Author

gedw99 commented Jan 7, 2022

I plan to work on it .

zinc does not yet provide all of the API but it’s does cover done of it .

@gedw99
Copy link
Author

gedw99 commented Jan 7, 2022

Cc

@prabhatsharma

@wbeckler
Copy link

Given @mosuka's intention to create a different kind of database without all of the methods of opensearch, I propose we close this Issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants