-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Comments
What is the action time on this? Add to docs? |
Yes, once it's out of the prototype phase. It's also referenced from the main storage backends ticket #638, so discoverable even now. |
@chvck any updates on the status of this work? |
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). |
@chvck any news on this? |
@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. |
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. |
Early prototype by @chvck
#638 (comment)
The text was updated successfully, but these errors were encountered: