My team has been writing a dashboard application using Node.js, Twitter Boostrap, Mongo DB, and Mule for an ESB.
我的团队一直在使用Node.js，Twitter Boostrap，Mongo DB和Mule为ESB编写仪表板应用程序。
Recently an executive asked us to change our approach to a Portal/Portlet container like Liferay.
最近，一位高管要求我们改变我们对像Liferay这样的Portal / Portlet容器的方法。
Some of us on the team have experience with Liferay, and we have pretty negative feelings about it. Dealing with things like full-page refreshes, portlet lifecycles, style and theming issues, and limited DBMS coverage are at the top of our list of complaints.
我们团队中的一些人有Liferay的经验，我们对此有非常消极的感受。处理完整页面刷新，portlet生命周期，样式和主题问题以及有限的DBMS覆盖率等问题是我们的投诉列表中的首要问题。
We see where our executive team is coming from. They have decided that they want to make the dashboard extensible and easy or easier to plug into for other groups.
我们看到我们的管理团队来自哪里。他们决定让他们想要使仪表板可扩展，轻松或更容易插入其他组。
Is there a solution out there which can balance the modern web expectations of users with the enterprise needs of IT professionals and executives concerned with building and extensible application with something like Liferay? Pluggable widgets are important here.
有没有一个解决方案可以平衡用户的现代Web期望与IT专业人员和负责构建和扩展应用程序的管理人员的企业需求，如Liferay？可插拔小部件在这里很重要。
Node would obviously be our preference with something like Grails as a close second.
节点显然是我们的偏好，像Grails这样的东西紧随其后。
Thanks,
谢谢，
1 个解决方案
#1
0
This question may not exactly be a good fit for *'s format, but I can offer some thoughts still.
这个问题可能不完全适合*的格式，但我仍然可以提供一些想法。
If you want to stick your current platform, you need to figure exactly what features your executives want to get out of moving to a new platform. Are those features something you can build into your current platform? How much effort will that take compared to rewriting everything else? How effort will it take to learn a new skillset across your whole team? I'm sure your team can learn the new skills effectively but that still takes effort and there will be growing pains as your teams learns. If you can show to your executives that you can get the same features for a similar or less effort and that you can still have similar total cost of ownership, you can make a case to stay on your current platform.
如果您想坚持当前的平台，您需要准确确定您的高管希望从哪个功能转移到新平台。这些功能是否可以构建到当前平台中？与重写其他所有内容相比，需要花费多少精力？如何努力学习整个团队的新技能？我相信你的团队可以有效地学习新技能，但仍然需要付出努力，随着你的团队学习，会有越来越多的痛苦。如果您可以向您的管理人员表明，您可以通过类似或更少的工作获得相同的功能，并且您仍然可以拥有相似的总体拥有成本，那么您可以建立一个案例来保持当前的平台。
Also I think you are underestimating what a Portlet container can do. I work mostly with WebSphere Portal so maybe thats why I think most of the pain points you mentioned really aren't that difficult to manage for me. Just because your container needs a particular DBMS to manage itself does not mean you can't use a separate DB for your custom data needs. JSR-286 introduced serveResource as a way to make AJAX easier to implement in portlets. In WebSphere Portal (don't know about Liferay), changing out the whole page content without a page reload might the most difficult on your list I'll admit though.
另外我认为你低估了Portlet容器的功能。我主要使用WebSphere Portal工作，所以也许这就是为什么我认为你提到的大多数痛点对我来说并不困难。仅仅因为您的容器需要特定的DBMS来管理自身并不意味着您不能使用单独的数据库来满足您的自定义数据需求。 JSR-286引入了serveResource作为一种使AJAX更容易在portlet中实现的方法。在WebSphere Portal中（不了解Liferay），在没有页面重新加载的情况下更改整个页面内容可能是您在列表中最难以承认的。
Modern doesn't have to mean bleeding-edge tech. And the large software products can still perform if you know how to use them right, just like any other tool.
现代并不一定意味着尖端技术。如果您知道如何正确使用它们，大型软件产品仍然可以执行，就像任何其他工具一样。
#1
0
This question may not exactly be a good fit for *'s format, but I can offer some thoughts still.
这个问题可能不完全适合*的格式，但我仍然可以提供一些想法。
If you want to stick your current platform, you need to figure exactly what features your executives want to get out of moving to a new platform. Are those features something you can build into your current platform? How much effort will that take compared to rewriting everything else? How effort will it take to learn a new skillset across your whole team? I'm sure your team can learn the new skills effectively but that still takes effort and there will be growing pains as your teams learns. If you can show to your executives that you can get the same features for a similar or less effort and that you can still have similar total cost of ownership, you can make a case to stay on your current platform.
如果您想坚持当前的平台，您需要准确确定您的高管希望从哪个功能转移到新平台。这些功能是否可以构建到当前平台中？与重写其他所有内容相比，需要花费多少精力？如何努力学习整个团队的新技能？我相信你的团队可以有效地学习新技能，但仍然需要付出努力，随着你的团队学习，会有越来越多的痛苦。如果您可以向您的管理人员表明，您可以通过类似或更少的工作获得相同的功能，并且您仍然可以拥有相似的总体拥有成本，那么您可以建立一个案例来保持当前的平台。
Also I think you are underestimating what a Portlet container can do. I work mostly with WebSphere Portal so maybe thats why I think most of the pain points you mentioned really aren't that difficult to manage for me. Just because your container needs a particular DBMS to manage itself does not mean you can't use a separate DB for your custom data needs. JSR-286 introduced serveResource as a way to make AJAX easier to implement in portlets. In WebSphere Portal (don't know about Liferay), changing out the whole page content without a page reload might the most difficult on your list I'll admit though.
另外我认为你低估了Portlet容器的功能。我主要使用WebSphere Portal工作，所以也许这就是为什么我认为你提到的大多数痛点对我来说并不困难。仅仅因为您的容器需要特定的DBMS来管理自身并不意味着您不能使用单独的数据库来满足您的自定义数据需求。 JSR-286引入了serveResource作为一种使AJAX更容易在portlet中实现的方法。在WebSphere Portal中（不了解Liferay），在没有页面重新加载的情况下更改整个页面内容可能是您在列表中最难以承认的。
Modern doesn't have to mean bleeding-edge tech. And the large software products can still perform if you know how to use them right, just like any other tool.
现代并不一定意味着尖端技术。如果您知道如何正确使用它们，大型软件产品仍然可以执行，就像任何其他工具一样。