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

Couchbase as storage backend #1575

Closed
yurishkuro opened this issue May 31, 2019 · 7 comments
Closed

Couchbase as storage backend #1575

yurishkuro opened this issue May 31, 2019 · 7 comments

Comments

@yurishkuro
Copy link
Member

Early prototype by @chvck

#638 (comment)

I just thought that I'd drop something here to say that there is also support for using Couchbase as a storage backend (via the grpc plugin), currently at https://github.com/chvck/couchbase-jaeger-storage-plugin. Will likely move to the couchbase-labs organisation in time.

@pavolloffay
Copy link
Member

What is the action time on this? Add to docs?

@yurishkuro
Copy link
Member Author

Yes, once it's out of the prototype phase. It's also referenced from the main storage backends ticket #638, so discoverable even now.

@yurishkuro
Copy link
Member Author

@chvck any updates on the status of this work?

@yurishkuro yurishkuro added the help wanted Features that maintainers are willing to accept but do not have cycles to implement label Jul 18, 2019
@chvck
Copy link
Contributor

chvck commented Jul 23, 2019

Hi @yurishkuro we're currently working on trying to improve visibility of the plugin so that we can progress it further. I'm hoping to get chance to publish a combined docker image of Jaeger all-in-one and the plugin this week to make it more accessible (the Dockerfile exists already).

@yurishkuro
Copy link
Member Author

@chvck any news on this?

@chvck
Copy link
Contributor

chvck commented Dec 27, 2019

@yurishkuro unfortunately very similar status to before. We have released a docker image of the Jaeger all in one plus the plugin although it's currently under my personal account. We also have a docker composer file that runs Couchbase, Jaeger and the plugin together to try make evaluation as easy as possible.

Do you have any ideas on how we can improve visibility and uptake to help drive the development forward? I should have some time in January to try make things happen.

@yurishkuro
Copy link
Member Author

I think you need to have a business case for why this backend is needed. Certainly some people are more familiar with some databases than others, but that is not a strong reason to maintain a dozen implementations, same efforts would be better spent on making fewer implementations better. However, some DBs may present features that provide a unique edge in either functionality or performance. If those benefits are clearly spelled out and quantified, that may raise more interest. Otherwise for someone who stumbles upon Jaeger there is little incentive to invest time in getting an external plugin working vs. using the officially supported backends.

@yurishkuro yurishkuro removed hacktoberfest help wanted Features that maintainers are willing to accept but do not have cycles to implement labels Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants