J2EE web服务的可扩展性如何实现？
我有这个 Web 客户端（完全通过 Javascript Ajax 框架构建），它通过 Web 服务调用与中间层通信（3 个 Web 服务部署在 JBoss 上，1 个 Web 服务部署在 Tomcat 上）。所有 Web 服务都访问同一个 Oracle 数据库。 Web 服务是通过 Axis2 和 Spring 构建的。所有服务都部署在一台机器上，数据库部署在另一台机器上。
我开始运行一些 SoapUI 负载测试，并注意到一旦超过 200 个并发用户标记，系统就会开始丢弃许多连接。我应该研究哪些可扩展性方法来优化系统以处理更多的用户？我知道可扩展性是一个非常广泛的问题，但是，您能否向我提供我应该开始研究和学习的关键领域列表？
谢谢！
I have this web client (built entirely through a Javascript Ajax framework), that communicates with the middle tier via web service calls (3 web services are deployed on JBoss, 1 web service is deployed on Tomcat). All of the web services access the same Oracle database. The web services are built through Axis2 and Spring. All the services are deployed on 1 machine, the database on another.
I started running some SoapUI load tests, and noticed that the system starts dropping many connections once it reaches beyond the 200 concurrent users mark. What scalability approaches should I be researching in order to optimize the system to handle much larger volume of user? I know scalability is a very broad issue but, could you please provide me with a list of key areas I should start looking into and learning about?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
多个应用程序服务器之间的负载平衡。有多种方法可以做到这一点，具体取决于您对多站点多服务器可靠性的关心程度以及对纯粹性能扩展的程度。
Load balance across multiple application servers. There are several ways to do this, depending on how much you care about multi-site multi-server reliability and how much about pure performance scaling.