2010-03-02 21:07
浏览 61


For my new heavy database read application ,i need to use GWT and mysql. But in choosing between java and PHP,i have some confusions, 1)JDBC with mysql is slower than PHP with mysql (PHP won) 2)if am going to use PHP ,i have to use JSON for transferring data between server and client. 3)This json parsing and handling overhead can be easily replaced by fast RPC calls if am using JAVA.(JAVA own) 4)GWT has lot of support and small frameworks for JAVA/RPC calls,so productivity is higher.

Please help me to choose a good one.

图片转代码服务由CSDN问答提供 功能建议

对于我的新的重型数据库读取应用程序,我需要使用GWT和mysql。 但是在java和PHP之间进行选择 我有一些困惑, 1)使用mysql的JDBC比使用mysql的PHP慢(PHP赢了) 2)如果要使用PHP,我必须使用JSON在服务器和客户端之间传输数据。 3)这个json 如果使用JAVA,快速RPC调用可以很容易地替换解析和处理开销。(JAVA拥有) 4)GWT对JAVA / RPC调用有很多支持和小框架,因此生产率更高。 \ n


  • 写回答
  • 关注问题
  • 收藏
  • 邀请回答

7条回答 默认 最新

  • dongzi3805 2010-03-02 21:23

    I think both of them are very suitable. While I understand that your need for performance is an important issue, I personally think, neither the SQL driver nor the JSON parsing will be your performance problem later on.

    With most AJAX calls, the network overhead (TCP handshake etc) takes up most of the time unless you have large files to transfer. And then it does not matter what the backend is.

    If you use Java and an Application Server, your database connections should be pooled and fast. If you use GWT RCP, you can easily refactor your application if you need to make changes later, a big plus. If you find out some of your updates are two slow, the biggest performance boost might come from caching data on the client and/or combining AJAX calls. This refactoring is a lot easier if you use Java on both, the client- and server side.

    打赏 评论
  • doumei3828 2010-03-02 21:09

    I think it really depends on what you want to write it in and what you want to maintain it in. Personally I'd use PHP because I'm personally more familiar with PHP.

    打赏 评论
  • douhe1002 2010-03-02 21:17

    GWT is a framework to create Web application using Java code. You can connect it to a PHP backend (and there's documentation on how to do it) But, from my point of view then you're losing the main point of GWT, one single language for your whole app.

    If you really need to use GWT for your frontend, also do your backend in Java. If you take a different approach, then use PHP+HTML+JavaScript.

    My 2 cents.

    打赏 评论
  • dongmou9260 2010-03-02 21:25

    I would stick to Java as that is the official GWT language. If you use PHP you lose out on the benefits of using powerful Java IDEs like Eclipse and IntelliJ Idea for development and debugging.

    打赏 评论
  • dongliao4353 2011-12-19 17:26

    One important point which I think has been missed here is cost. If you use PHP your hosting costs will potentially be considerably less. Adding Java to the equation usually means starting with a dedicated server or VM, (remember the Java-developed GWT front-end is compiled to Javascript). Ignoring cost Java would seem the obvious choice of the two, for reasons mentioned above mainly, one language and easier RPC.

    打赏 评论
  • duan20081202 2012-07-06 06:38
    打赏 评论
  • doujin8476 2012-12-15 12:26

    IF you use PHP for backend, you can not use "GWT rpc", you can only use asynchronous HTTP request (using RequestBuilder), but your hosting costs will decrease. I think it is better you implement you backend using REST services (by PHP) and then call those services by your GWT application at the frontend (for example using restygwt library). With this approach you can change your backend technology (or frontend technology) easily in the future.

    Have a nice time.

    打赏 评论

相关推荐 更多相似问题