简体   繁体   English

网络应用架构

[英]web application architecture

We have an existing app which is mostly JSP based for front end and Java/DAO based back end connecting to an oracle DB. 我们有一个现有的应用程序,该应用程序主要是基于JSP的前端和连接到oracle DB的基于Java / DAO的后端。 This is an enterprise level trading application. 这是企业级交易应用程序。

Recently our management gave directive to use GWT to have a more modern look and feel to our front end pages. 最近,我们的管理人员指示使用GWT使前端页面具有更现代的外观。 So we have migrated a few existing pages to GWT as well as all brand new development is in GWT. 因此,我们已经将一些现有页面迁移到GWT,并且所有全新的开发都在GWT中。 GWT is being used for both rendering front end as well as server side communications and AJAX. GWT用于渲染前端以及服务器端通信和AJAX。

However, I am concerned about fully embracing GWT as it is a client side architecture where most of the rendering logic processing happens on the client side. 但是,我担心完全拥抱GWT,因为它是一种客户端体系结构,其中大多数呈现逻辑处理都发生在客户端。

  1. Is my concern justified? 我的担心合理吗?

  2. What other architectures would you recommend? 您还会推荐其他哪些架构? Spring MVC/Webflow? Spring MVC / Webflow? Something else? 还有吗

Is my concern justified? 我的担心合理吗?

No. 没有。

Doing less work on the server means doing more requests per second. 在服务器上减少工作量意味着每秒执行更多请求。

I'd start with a service architecture. 我将从服务架构开始。 Keep the processing in the back so you can swap UIs in and out without rewriting the back end. 将处理保留在后台,这样您就可以在不重写后端的情况下切入和切出UI。

They can be SOAP or REST. 它们可以是SOAP或REST。 You need not make them heavy. 您无需使其沉重。

Best to not depend on JSP or GWT for the processing. 最好不要依赖JSP或GWT进行处理。 Ever hope to make this available on iPad? 曾经希望在iPad上提供此功能吗? It'd be good to be able to do it without rewriting the whole thing. 无需重写整个过程就可以做到这一点。

Start with coarse-grained services that match your use cases. 从与您的用例相匹配的粗粒度服务开始。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM