-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Shared DevServices Container for MongoDB Like Kafka in Quarkus #38678
Comments
/cc @alesj (kafka), @cescoffier (kafka), @geoand (devservices), @loicmathieu (mongodb), @ozangunalp (kafka), @stuartwdouglas (devservices) |
It should be possible without too much trouble. Fancy a PR if we guide you? |
@cescoffier what about if we try it with the new "dev resources" concept? |
I could address this request, similarly, as it was done for redis, kafka and others, eg: #18029 - if this is still acceptable. |
@patrox definitely! |
@patrox @cescoffier do I understand it correctly, that this issue is fixed? If so when will it be delivered? |
No it has not been fixed yet. |
@Inithron I'm close to completing it, hopefully, it shouldn't take too long - expect a PR within a week! |
Added a PR that should address this issue: #39787 @loicmathieu Can I please kindly ask you for a review? |
Is there any progress on this issue? |
Hi @patrox, hi @gsmet,
So my question now: Is the issue not solved properly, or is it still not part of version 3.12? |
Same behavior with version 3.12.1. Should i create a new issue that the shared-server is not working? |
@patrox can you have a look please? |
Hi,
As a short summary: Due to the case that many extensions are affected by this issue, it would be great to solve this issue in a central place, if possible. If not maybe the contributors of the different extensions could support each other to solve the issues for each extension individually. |
Hello, Although the desire to have the issue(s) addressed it totally understandable, it is pretty counterproductive to copy and paste the comment across various issues. Thanks |
Hi @geoand, |
No problem 😃 |
Description
I am working on a Quarkus application that consists of several components. I've noticed that while using DevServices for Kafka a shared single container across all components is used, which is efficient and resource-saving. However, for MongoDB, each component spawns its own container, leading to increased resource consumption on local dev computer.
I would like to request a feature for Quarkus DevServices that allows MongoDB to behave similarly to Kafka in terms of container sharing. Specifically, the ability to configure MongoDB DevServices to use a single shared container across multiple application components, instead of creating a separate container for each component. This feature should be configurable, allowing developers to choose between shared and individual containers based on their specific needs.
Configuration idea:
quarkus.mongodb.devservices.shared=true
quarkus.mongodb.devservices.shared-container-name=myMongoDevContainer
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: