JSF 真的准备好迎接高性能社交网络项目了吗？
我听说过很多关于 JSF 的好消息，但据我所知，人们过去也对这项技术提出过很多严重的抱怨，但不知道情况已经改善了多少。我们正在考虑将 JSF 作为社交网络项目的一种可能技术。但我们不知道 JSF 的性能分数，也无法真正遇到任何使用 JSF 的现有高性能网站。人们抱怨它太慢了关于其可扩展性问题。
我们仍然不太确定选择 jsf & 是否正确。因此想听听您关于此事的一切信息&考虑您的意见。至于后端，我们将使用 NoSQL 数据库。
I have heard a lot of good about JSF but as far as I know people also had lots of serious complains with this technology in the past, not aware of how much the situation has improved. We are considering JSF as a probable technology for a social network project. But we are not aware of the performance scores of JSF neither we could really come across any existing high performance website that had been using JSF. People complain that it is too slow & about its scalability issues.
We are still not very sure if we are doing the right thing by choosing jsf & thus would like to hear from you all about this & take your inputs into consideration. As for the backend we are going with a NoSQL database.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这只是我的观点，但是高性能社交网络通常需要大量的客户端代码调整，如果您尝试使用 jsf 来做到这一点，这可能会让您头疼。 JSF 涉及组件的可重用性以及从开发人员那里抽象出 JavaScript、ajax、资源加载等黑魔法，有时会导致访问组件的内部变得困难。
It's just my opinion, but high performance social networks usually need a great deal of client side code tuning, something that can give you a headache if you try to do it twith jsf. JSF is about reusability of components and abstracting black magic like javascript, ajax, resource loading etc, from developer and sometimes makes access to internals of the components difficult.
我不会推荐 JSF。我最后一次看到它已经是三年前了。您可以使用日晷来计时一个简单应用程序的页面加载时间。
诚然，JSF 迷会说做这件事的人不熟练。但我想知道为什么这样的东西可以使用得这么糟糕。
我建议使用基于服务的 REST 架构，该架构使用基于 HTML5、CSS 和 JavaScript 的干净 UI。我将使用 Spring 实现前者，使用 Velocity 视图或 jQuery 模板实现后者。
I would not recommend JSF. The last time I saw it was three years ago. You could time the page loading time for a simple app with a sundial.
Admittedly, a JSF junkie would say that the folks who did it weren't skilled. But I'd wonder why it's possible to use such a thing so badly.
I would recommend a service-based REST architecture that used a clean UI based on HTML5, CSS, and JavaScript. I'd implement the former with Spring and the latter with Velocity view or jQuery templates.