blocks|key|1199488|text|如果您对Java感到满意，那么我认为没有必要学习/使用PHP。PHP可以做任何Java不能做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1199489|总的来说，PHP确实是一种更宽松的语言，一些任务可以用更少的代码更快地完成。PHP的内置抽象当然比Java少。但是如果你对Java感到满意，我会建议你坚持使用它。|1199490|(我是以PHP开发人员的身份这么说的。)|1199491|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you're comfortable with Java, I don't see the need to learn/use PHP. There is nothing that PHP can do that Java can't. 

It's true that by and large, PHP is a much more permissive language, and some tasks can be fulfilled more quickly and with less code. PHP certainly has less built-in abstraction than Java has. But if you're comfortable with Java, I'd say stick with it. 

(I'm saying this as a PHP developer.)

blocks|key|1944688|text|如果你懂java，那就用JPA吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1944689|如果你想学习一些新的、快速的原型设计，可以使用python/django。|1944690|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

IMHO if you know java, use JPA.

If you want to learn something new and fast prototyping, use python/django.

blocks|key|3365860|text|这里真正的问题是，你需要库来让你的工作变得更容易。JVM作为一种平台比PHP有更多的选择，如果没有其他原因，您可以将您的应用程序与嵌入式语言混合。此外，Hibernate作为一种ORM+(对象关系映射)非常出色，它基本上将表视为POJO。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3365861|如果你在做很多“原始”的东西，我其实很喜欢使用Sequel，它是一个Ruby库，在JRuby上运行得很好。总的来说，我发现人们喜欢的打字/简洁的代码绝对可以通过JRuby+(对于Python爱好者来说是Jython+)复制到Ruby语言中。|3365862|最好的库将取决于您正在处理的模式的趣味性，以及您正在做的工作的类型。您是否需要执行大量复杂的查询，一次从多个表中提取列？或者更像是“我需要获取某个客户的所有订单并将其显示在订单历史记录图表中”？ORM更适合后者，这是web应用程序倾向于的，但您提到的解析和分析让我想知道它是不是更像前者。|3365863|我发现Hibernate给了你最大的灵活性。不审阅就使用自动生成的东西并不是一个好主意，但是如果您使用Eclipse，有一个插件可以为您生成类。|3365864|使用Java的另一个原因是:如果您查看web应用程序的Glassfish容器，它已经为您构建了JDBC池，您可以查看池的统计数据和管理。如果你有很多数据库访问，这可能是非常有用的。|3365865|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Well, the real issue here is that you need libraries to make your work easier. JVM as a platform has many more options than PHP, if for no other reason than you can hybridize your application with embedded languages. Also, Hibernate is fantastic as an ORM (Object Relational Mapping), basically taking your tables and looking at them as POJOs. 

If you're doing lots of 'raw' stuff, I actually like using Sequel, which is a Ruby library and works very well on JRuby. In general, I find that the duck-typing/concise code that people like about PHP is absolutely replicable in Ruby via JRuby (or Jython for you Python enthusiast types). 

The best library is going to be dictated by the funkiness of the schema you're dealing with, in addition to the type of work you're doing. Do you need to do lots of complicated queries, fetching columns from several tables all at once? Or is it more along the lines of "I Need to fetch all the Orders for a certain customer and display it in an order history chart"? ORMs are better suited to the latter, which is what web apps tend to be, but your mention of parsing and analyzing makes me wonder if it's more the former. 

Hibernate gives you the greatest flexibility, I find. It's not a good idea to use autogenerated stuff without reviewing it, but if you use Eclipse, there's a plugin that will generate the classes for you. 

Another reason to go with Java: If you look at the Glassfish container for your web application, it has built in JDBC pools for you and you can look at the statistics and management of the pool. If you have a lot of database access, this could be pretty useful.

blocks|key|3365883|text|我认为没有必要使用PHP，你可以使用你认为是web应用程序的Java.If，然后你就可以使用PHP.So了，你可以从任何地方访问它|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3365884|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think there is no need for PHP , you can just go with Java.If you consider that application to be a web application then you can use PHP.So you can access it from anywhere

blocks|key|3365979|text|PHP可以让你用比Java更少的工作量和更少的代码行来做很多web事情，我想(我只是在说我自己的经验--总是有人告诉你“使用Java，PHP是垃圾”，还有一些人会告诉你"PHP比Java好得多“。不要听我们的，试一试，否则你永远不会知道！)我做了很多Java的事情，但就web应用而言，我对此并不满意。对于我们的大多数客户来说，也不可能使用Java，所以我也没有太多的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3365980|有一些很好的PHP框架(例如，Yii，我最喜欢它)，也有非常好的or作为原则或活动记录。如果你必须学习这门语言，并且对敏捷开发感兴趣，也可以考虑Ruby+(Ruby+on+Rails)或Python+(Django)，因为这些都是镇上很酷的孩子:)|3365981|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

PHP lets you do a lot of web things with less effort and fewer lines of code than Java does, I think (and I'm only talking about my own experience - there are always some who tell you "Use Java, PHP is crap" and there will be the ones to tell you "PHP is so much better than Java". Don't listen to us, simply try it or you will never know!). I do a lot of Java stuff, but as far as web apps are concerned, I'm not happy with it. For most of our customers, it's not possible to use Java, too, so I don't have that much of a choice, anyway.

There are some good PHP frameworks out there (Yii for example, which I like most) and really good orms as doctrine or active record. If you have to learn the language and are interested in agile development, also think about Ruby (Ruby on Rails) or Python (Django) as these are the cool kids in town :)

blocks|key|3366014|text|为什么不同时使用两者呢？Quercus将在Java中运行PHP。您可以像调用原生PHP函数一样调用Java代码。你可以两全其美。而且你的PHP实际上会比在Apache下运行得更快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3366015|我是一名PHP程序员，虽然PHP+DB访问协议可能更“简单”(有争议)，但我不会说它们更好。Java可以使用DB连接池，并且可以“持久化”数据、代码和对象。|3366016|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Why not use both? Quercus will run PHP in Java. You can call Java code as if it was native PHP functions. You get the best of both. And your PHP will actually run faster than under Apache.

I'm a PHP programmer, and while PHP DB access protocols may be "simpler" (debatable), I wouldn't say they are better. Java can use DB connection pooling and can "persist" data, code and objects.

blocks|key|3366070|text|这两种语言的语法、语言和实现之间存在着巨大的差异。我认为“使DB访问协议变得更简单”并不是孤立地选择一种语言而不是另一种语言的一个特别好的理由。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3366071|我的背景是PHP程序员，但我目前支持几个大型Java+web应用程序。如果你是从这两种语言的同一点开始的，那么我肯定更喜欢PHP而不是Java+-但是充分讨论为什么会花费比这里可用的时间和空间更多的原因。但是，如果您已经掌握了很强的Java技能，那么您必须权衡获得适当水平的PHP技能的成本-由于这些系统的工作方式不同，您会发现Java知识既是精通PHP的有利因素，也是阻碍因素。|3366072|我建议您考虑的其他因素包括：|3366073|1)架构--+PHP需要比Java更好地理解底层协议(其中很多功能是由libs/+framework提供的)|3366074|2)易于部署|3366075|3)性能考虑-使用操作码缓存意味着用Java和PHP编写的简单程序之间的差异很小，因为前者通常是在非常复杂的框架内编写的，PHP通常具有优势。它当然没有内存管理那么复杂。|3366076|4)+TCO+-+PHPs易用性是一把双刃剑--你需要了解很多关于Java的知识才能运行一个程序，但是全世界和他的狗都认为他们可以用PHP写出好的代码。比起Java程序员，更难找到称职的PHP程序员。|3366077|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

There is a huge amount of difference between the syntax, phuilosophy and implementation of the 2 languages. I would suggest that "makes DB access protocols a lot simpler" is not a particularly good reason in isolation for choosing one language over another.

My background is as a PHP programmer, but I currently support several large Java web applications. If you were starting from the same point with both languages then I'd definitely favour PHP over Java - but a full discussion of the reasons why would take a lot more time and space than are available here. However if you already have strong Java skills, then you have to weigh up the costs of acquiring the right level of skill in PHP - due to the differences in the way these systems work, you're going to find your knowledge of Java as much of a hindrance as a benefit in achieving proficiency in PHP.

Other factors I would suggest you have a look at are:

1) architecture - PHP requires far better understanding of the underlying protocols than Java (where a lot of functionality is provided by libs/ frameworks)

2) ease of deployment

3) performance considerations - using an opcode cache means the difference between simple programs written in Java and PHP is small, since the former are usually written inside very complex frameworks, PHP can often have the edge. It certainly does not have the same complexity for memory mngmnt

4) TCO - PHPs ease of use is a double edged sword - you need to know a lot about Java just to get a program running, but the world and his dog think they can write good code in PHP. IME its more difficult to find competent PHP programmers than Java programmers.

blocks|key|4777039|text|对我来说，这归结于性能。当你观察PHP时，它肯定已经部署在非常大的平台上(Facebook在一开始几乎只使用它)，但通常它被用在较小的平台上。Java，对我来说，当你看到它的可伸缩性好处时，它是优越的，但只有当你知道你要伸缩的时候。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4777040|理解请求的底层生命周期非常重要。也就是说，了解什么是Java容器以及Tomcat服务器是如何运行的帮助我极大地理解了性能方面的影响。|4777041|不要试图在诸如“编码的简易性”或“数据库连接性”这样的单一属性上进行选择-它们有足够的不同，通过只关注几个“重要”的事情，你实际上将根据有偏见的信息进行选择。也就是说，PHP使连接到DB变得更容易，如果你从表面上看它们-“啊！我必须安装JDBC，wtf是不是？”等等-但这是懒人的借口。Java没有PHP不能做的事情(据我所知)。|4777042|对我来说，问题是你如何realistically+(Read:+realistically)看到你的应用程序工作-你是计划每小时有成千上万的访问量，还是像绝大多数小项目那样每天有100次点击？|offset|length|style|BOLD|4777043|PHP在较小的项目中的好处是巨大的，特别是对于没有完全掌握OOP架构的程序员-但不要偷懒，只使用PHP，因为它更容易开箱即用。Java非常强大，仅仅通过学习它就可以教给您更多关于OOP和良好编程实践的知识(如果您来自自学成才的领域，就像我一样)。|4777044|基本上，如果你必须学习其中一个，我会说分析你估计的项目负载和升级时间，评估你的效率和可扩展性需求，不断提出问题，然后决定哪个平台更好。|4777045|希望这能帮上忙...！|4777046|entityMap^0|0|0|0|B|D|Q|J|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@$H|X|I|Y|J|K]|$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|S|$]]

For me this comes down to performance. When you look at PHP it has certainly been deployed on extremely large platforms (Facebook used it almost exclusively at the beginning), but in general it is used on smaller platforms. Java, for me, when you look at it's scalability benefits is superior, but only when you know you're going to be scaling. 

Understanding the underlying life cycle of a request is very important. That is, knowing what a Java container is and how a Tomcat server runs helped me understand tremendously the performance implications.

Don't try to choose one over the other over single attributes such as "ease of coding" or "database connectivity"- they are different enough that by focusing on just a couple of "important" things you'll be essentially selecting based off of biased information. That is, PHP makes it easier to connect to a DB if you look at them on a surface level- "Ugh! I have to install a JDBC, wtf is that???", etc- but that's the lazy man's excuse. There is nothing Java can't do that PHP can (that I'm aware of). 

For me the question is how do you realistically (Read: realistically) see your application working- do you plan on getting thousands of visits per hour or are you talking a hundred hits a day like the grand majority of the little projects out there?

The benefits of PHP on smaller projects, particularly for the programmer that doesn't fully grasp OOP architecture are enormous- but don't get lazy and just take PHP because it's easier out of the box. Java is extremely powerful and simply by learning it can teach you more than you realized you didn't know about OOP and good programming practices in general (if you come from the self-taught realm like I do).

Basically, I'd say analyze your estimated project load plus ramp-up time if you have to learn one or the other, gauge your efficiency and scalability requirements, keep asking questions, and then decide which platform is better. 

Hope that helps....!

I am creating a web app that involves a lot of DB access and parsing and analysing data , Java is the language i am most comfortable with but recently have been told that I should consider to use PHP as it makes DB access protocols a lot simpler.

I dont have any great knowledge of PHP but would be willing to learn for use if it was going to be the better option as far as functionality , portability ect is concerned.

The Web app will run against an Oracle DB and use Flex for the GUI, Please any experiences of similar projects and what made your chosen approach better would help or just opinions of any sort.

Java OR PHP Server Side Web App and Why?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在创建一个涉及大量数据库访问以及解析和分析数据的web应用程序，Java是我最熟悉的语言，但最近有人告诉我，我应该考虑使用PHP，因为它使数据库访问协议变得简单得多。我没有任何PHP的伟大知识，但我愿意学习使用，如果它是功能，可移植性等方面的更好的选择。Web应用程序将在Oracle数据库上运行，并使用Flex f...

问Java还是PHP服务器端Web应用，为什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java还是PHP服务器端Web应用，为什么？EN