det101 commented on issue #17252: URL: https://github.com/apache/dolphinscheduler/issues/17252#issuecomment-2968934886
> > My proposal is mainly to optimize the debugging and release process under the existing system. Of course, if namespaces are introduced, the isolation may be more thorough, and the isolation of the data warehouse environment may also need to be considered. This is a huge project that requires more people to participate. > > A more comprehensive and perfect scheme should be considered. In the future, when we continue to expand related functions, we don't need to carry out comprehensive reconstruction. I don't think it is advisable to bury a hole in the future in order to introduce a feature. I learned about DataWorks, and it doesn't have the concept of projects. Its namespace is the workflow. In addition, its project space is physically isolated, which is reasonable on the public cloud. Can we balance the benefits and complexity of introducing namespaces on the project? And it is impossible to achieve physical isolation. There should be no public cloud model for using DS (of course, we have also modified the DS cloud, and the worker is opened on the user vpc, but there is no problem with the workspace for the time being). 我学习了下dataworks，他没有项目的概念，他的命名空间下面就是工作流。另外他的项目空间是做物理隔离的，这在公有云上是合理的； 我们在项目上面再引入命名空间能带来的收益和复杂度是否能平衡，而且也无法实现物理隔离，使用DS应该还没有公有云的模式（当然我们也把DS云上做了改造，worker在用户vpc上开，但还没有引工作空间暂时也没有问题） -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
