You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@rocketmq.apache.org by Jie Tang <st...@apache.org> on 2021/08/23 12:54:35 UTC
Rocketmq Dashboard architecture upgrade
Hi All, RocketMQ Console was renamed to RocketMQ Dashboard and transferred
to rocketmq-dashboard <https://github.com/apache/rocketmq-dashboard> , we
want to upgrade the RocketMQ Dashboard's architecture to make it easy to
add features and maintain.
At first we want to separate the front end and back end module. backend
still using spring-boot, for front end we can choose a fancy framework to
replace angular 1.0, details can be found Front End / Back End separate
solution <https://github.com/apache/rocketmq-dashboard/issues/10>
About new front end framework, we are still investigating it, we have
created Choose and setup front end framework
<https://github.com/apache/rocketmq-dashboard/issues/11> to track it.
Feel free to comment if you have any suggestions. Look forward to working
with you to make RocketMQ Dashboard better.
Thanks
回复: Rocketmq Dashboard architecture upgrade
Posted by Hu Zongtang <zo...@hotmail.com>.
Okay.
________________________________
发件人: Jie Tang <st...@apache.org>
发送时间: 2021年8月25日 0:01
收件人: dev@rocketmq.apache.org <de...@rocketmq.apache.org>
主题: Re: Rocketmq Dashboard architecture upgrade
> It will bring some maintain inconvenient if we separate the front end and
back end module. Because, open source users must deploy and maintain the
front end and back two parts.
We already found a way to only deploy spring-boot server, by using maven
plugin spring jar will contain both front end resource and backend
service. This PR already implements it, If there are any good suggestions
feel free to comment on it.
https://github.com/apache/rocketmq-dashboard/pull/12
> if we want upgrade the front part, maybe we can construct the front end
by Vue framework.
Good suggestion. Maybe we can use Vue/Angular instead of React. I created
an issue for the front end framework, we can discuss here.
https://github.com/apache/rocketmq-dashboard/issues/11
胡 宗棠 <zo...@hotmail.com> 于2021年8月24日周二 下午2:06写道：
> Very cool architecture upgrade!
>
> But I have some question belows:
>
> Firstly, it will bring some maintain inconvenient if we separate the front
> end and back end module. Because, open source users must deploy and
> maintain the front end and back two parts.
>
> Secondly, if we want upgrade the front part, maybe we can construct the
> front end by Vue framework.
>
> That's all. Thank you.
>
> ________________________________
> 发件人: Jie Tang <st...@apache.org>
> 发送时间: 2021年8月23日 20:54
> 收件人: users@rocketmq.apache.org <us...@rocketmq.apache.org>;
> dev@rocketmq.apache.org <de...@rocketmq.apache.org>
> 主题: Rocketmq Dashboard architecture upgrade
>
> Hi All, RocketMQ Console was renamed to RocketMQ Dashboard and transferred
> to rocketmq-dashboard <https://github.com/apache/rocketmq-dashboard> , we
> want to upgrade the RocketMQ Dashboard's architecture to make it easy to
> add features and maintain.
>
> At first we want to separate the front end and back end module. backend
> still using spring-boot, for front end we can choose a fancy framework to
> replace angular 1.0, details can be found Front End / Back End separate
> solution <https://github.com/apache/rocketmq-dashboard/issues/10>
>
> About new front end framework, we are still investigating it, we have
> created Choose and setup front end framework
> <https://github.com/apache/rocketmq-dashboard/issues/11> to track it.
>
> Feel free to comment if you have any suggestions. Look forward to working
> with you to make RocketMQ Dashboard better.
>
> Thanks
>
Re: Rocketmq Dashboard architecture upgrade
Posted by Jie Tang <st...@apache.org>.
> It will bring some maintain inconvenient if we separate the front end and
back end module. Because, open source users must deploy and maintain the
front end and back two parts.
We already found a way to only deploy spring-boot server, by using maven
plugin spring jar will contain both front end resource and backend
service. This PR already implements it, If there are any good suggestions
feel free to comment on it.
https://github.com/apache/rocketmq-dashboard/pull/12
> if we want upgrade the front part, maybe we can construct the front end
by Vue framework.
Good suggestion. Maybe we can use Vue/Angular instead of React. I created
an issue for the front end framework, we can discuss here.
https://github.com/apache/rocketmq-dashboard/issues/11
胡 宗棠 <zo...@hotmail.com> 于2021年8月24日周二 下午2:06写道：
> Very cool architecture upgrade!
>
> But I have some question belows:
>
> Firstly, it will bring some maintain inconvenient if we separate the front
> end and back end module. Because, open source users must deploy and
> maintain the front end and back two parts.
>
> Secondly, if we want upgrade the front part, maybe we can construct the
> front end by Vue framework.
>
> That's all. Thank you.
>
> ________________________________
> 发件人: Jie Tang <st...@apache.org>
> 发送时间: 2021年8月23日 20:54
> 收件人: users@rocketmq.apache.org <us...@rocketmq.apache.org>;
> dev@rocketmq.apache.org <de...@rocketmq.apache.org>
> 主题: Rocketmq Dashboard architecture upgrade
>
> Hi All, RocketMQ Console was renamed to RocketMQ Dashboard and transferred
> to rocketmq-dashboard <https://github.com/apache/rocketmq-dashboard> , we
> want to upgrade the RocketMQ Dashboard's architecture to make it easy to
> add features and maintain.
>
> At first we want to separate the front end and back end module. backend
> still using spring-boot, for front end we can choose a fancy framework to
> replace angular 1.0, details can be found Front End / Back End separate
> solution <https://github.com/apache/rocketmq-dashboard/issues/10>
>
> About new front end framework, we are still investigating it, we have
> created Choose and setup front end framework
> <https://github.com/apache/rocketmq-dashboard/issues/11> to track it.
>
> Feel free to comment if you have any suggestions. Look forward to working
> with you to make RocketMQ Dashboard better.
>
> Thanks
>
回复: Rocketmq Dashboard architecture upgrade
Posted by 胡 宗棠 <zo...@hotmail.com>.
Very cool architecture upgrade!
But I have some question belows:
Firstly, it will bring some maintain inconvenient if we separate the front end and back end module. Because, open source users must deploy and maintain the front end and back two parts.
Secondly, if we want upgrade the front part, maybe we can construct the front end by Vue framework.
That's all. Thank you.
________________________________
发件人: Jie Tang <st...@apache.org>
发送时间: 2021年8月23日 20:54
收件人: users@rocketmq.apache.org <us...@rocketmq.apache.org>; dev@rocketmq.apache.org <de...@rocketmq.apache.org>
主题: Rocketmq Dashboard architecture upgrade
Hi All, RocketMQ Console was renamed to RocketMQ Dashboard and transferred
to rocketmq-dashboard <https://github.com/apache/rocketmq-dashboard> , we
want to upgrade the RocketMQ Dashboard's architecture to make it easy to
add features and maintain.
At first we want to separate the front end and back end module. backend
still using spring-boot, for front end we can choose a fancy framework to
replace angular 1.0, details can be found Front End / Back End separate
solution <https://github.com/apache/rocketmq-dashboard/issues/10>
About new front end framework, we are still investigating it, we have
created Choose and setup front end framework
<https://github.com/apache/rocketmq-dashboard/issues/11> to track it.
Feel free to comment if you have any suggestions. Look forward to working
with you to make RocketMQ Dashboard better.
Thanks
Re: Rocketmq Dashboard architecture upgrade
Posted by tiger lee <ti...@apache.org>.
that's very nice.
IMO, for frontend
+1 Vue
-1 Angular
- 1 React
Jie Tang <st...@apache.org> 于2021年8月23日周一 下午8:54写道：
> Hi All, RocketMQ Console was renamed to RocketMQ Dashboard and transferred
> to rocketmq-dashboard <https://github.com/apache/rocketmq-dashboard> , we
> want to upgrade the RocketMQ Dashboard's architecture to make it easy to
> add features and maintain.
>
> At first we want to separate the front end and back end module. backend
> still using spring-boot, for front end we can choose a fancy framework to
> replace angular 1.0, details can be found Front End / Back End separate
> solution <https://github.com/apache/rocketmq-dashboard/issues/10>
>
> About new front end framework, we are still investigating it, we have
> created Choose and setup front end framework
> <https://github.com/apache/rocketmq-dashboard/issues/11> to track it.
>
> Feel free to comment if you have any suggestions. Look forward to working
> with you to make RocketMQ Dashboard better.
>
> Thanks
>