Spring 3.0 REST 实现还是 Jersey？
我目前正在尝试弄清楚我将向食物链的上游推荐哪种 JSR-311 实现。我几乎将其范围缩小到两个选项 - Spring 3.0 及其对 REST 的本机支持 - 或使用 Sun 自己的 Jersey（Restlets可能也是一个选项）。
对我来说，实际语法似乎没有太大区别，但可能存在我尚未弄清楚的性能问题。
该服务旨在取代一些重型 EJB，并创建 RESTful Web 服务。负载预计会相当高，达到每天 10 万用户（最大）范围，但会进行严格的负载平衡。
感谢您的所有见解。
I'm currently trying to figure out which implementation of JSR-311 I'm going to recommend further up the food chain. I've pretty much narrowed it down to two options - Spring 3.0 with it's native support for REST - or use Sun's own Jersey (Restlets might also be an option).
To me it doesn't seem to be much of a difference in the actual syntax, but there might be issues with performance that I haven't figured out yet.
The service is meant to replace some heavy-duty EJB's and make a RESTful Webservice instead. The load is expected to be rather high, up in the 100k users per day (max) range, but will be seriously load balanced.
Thanks for all your insights.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Spring 3 不是 JSR-311 的实现。也许这足以回答你的问题了？如果您希望在 Spring 上使用 JAX-RS，那么您无论如何都会使用（最有可能）Jersey 作为提供者！我认为，如果您已经是一家 EJB 商店，那么让每个人都学习 Spring MVC 的做法可能不太有用，如果 EJB3 是您的下一步？
这里有一篇文章！
http://www.infoq.com/articles/springmvc_jsx-rs
Spring 3 is not an implementation of JSR-311. Maybe that's enough to answer it for you? If you want JAX-RS on Spring, you'd be using (most likely) Jersey as the provider anyway! I would think if you're already an EJB shop, having everyone learn the Spring MVC way of doing it may not be too useful, if EJB3 is the next step for you?
Here's an article!
http://www.infoq.com/articles/springmvc_jsx-rs
您可能对 Spring 3.0 MVC 和 JAX-RS 的 InfoQ 比较感兴趣。
由于它是由“SpringSource 的高级顾问”撰写的，所以有点偏颇，但我认为这是对两种技术的公平和深入的比较。
You might be interested in this InfoQ comparison of Spring 3.0 MVC and JAX-RS.
It is a bit biased since it is written by "a senior consultant at SpringSource", but I think it's a fair and in-depth comparison of both technologies.