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

Rqueue decoupling and dependency lightweight management #246

Open
dylan-tao opened this issue Nov 22, 2024 · 1 comment
Open

Rqueue decoupling and dependency lightweight management #246

dylan-tao opened this issue Nov 22, 2024 · 1 comment
Assignees

Comments

@dylan-tao
Copy link

dylan-tao commented Nov 22, 2024

Is your feature request related to a problem? Please describe.
At present, rqueue as a component is a bit dependent.

Describe the solution you'd like
Split the module management of the runtime and management side; remove the three-party tool class dependency package and outdated and unpopular class packages. The current dependencies are too bloated. In addition, the template engine recommends replacing with JSTL and EL.

Describe alternatives you've considered
See the structure diagram below for details.

Additional context
rqueue

@sonus21
Copy link
Owner

sonus21 commented Dec 20, 2024

Rqueue controller requires various rqueue system status, though it makes sense to separate them for the cases where they don;t need the dashboard. As per my observations people needs Dashboard most of the time for debugging.

For other dependencies, I understand we can build and use them, is it causing any issue or something for you?

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

2 participants