blocks|key|1254499|text|我想说XML解决方案与数据库解决方案相比的主要缺点是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1254500|1254501|search+|ordered-list-item|1254502|1254503|+speed|1254504|scalability|1254505|concurrency+(感谢乔纳森)|1254506|1254507|1254508|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|-4|5|E|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|E|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|E|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|E|7|W|8|@]|9|@]|A|$]]|$1|M|3|-4|5|E|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|P|$]]

I would say the main disadvantages of the XML solution over a database one would be:

<ol>
<li>search speed</li>
<li>update speed</li>
<li>scalability</li>
<li>concurrency (thanks Jonathan)</li>
</ol>

blocks|key|4848695|text|轻量级是相对的。选择数据库解决方案。你永远不知道什么时候你的“轻量级”站点变成了“任务关键型”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4848696|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|$]]

Lightweight is relative. Go for the database solution. You never know when your "lightweight" site becomes "mission-critical"

blocks|key|4003263|text|PHP通常更广泛，也更受欢迎，因为它的学习曲线非常小，并且对于普通开发人员来说很容易学会并开始使用。它通常与基于linux的服务器上的大多数Apache安装捆绑在一起，这也不会有什么坏处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4003264|由于以上原因，有更多的好的(和坏的！)可用于帮助PHP初学者的资源比任何语言都要多，这就产生了滚雪球效应。|4003265|为了回答您最初关于XML的问题，在商品很少的小容量商店上的基本购物车实现可能不会使用您所描述的体系结构来分解，但是搜索商品数据库、跟踪库存等操作最好留给数据库。|4003266|也就是说，如果您已经在使用JSP，那么改用数据库并不意味着您需要放弃JSP。|4003267|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

PHP is generally more widespread and in demand because it has a very small learning curve and is easy for a casual developer to pick up and begin using. It also doesn't hurt that it usually comes bundled with most Apache installs on linux-based servers.

As a result of the above, there are many more good (and bad!) resources available to help a fledgling developer for PHP than just about any language out there, which creates a snowball effect.

To answer your original question concerning XML, a basic shopping cart implementation on a low-volume store with very few items probably wouldn't break down using the architecture you're describing, but actions like searching an item database, tracking inventory and such are best left to a database. 

That said, changing to a database doesn't mean you need to move off of JSP if that's what you're already working with.

blocks|key|1258693|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1258694|我有一个基于JSP和XML的轻量级在线购物网站，我想知道这个系统相对于PHP和MySQL有什么特别的弱点？|blockquote|1258695|1258696|1258697|JSP和PHP都是视图技术。JSP的优点是有强大的语言和平台Java+(EE)作后盾。PHP的优势在于它是有史以来最简单、最可公开采用的web编程语言。劣势不言而喻。|1258698|要开发一个遵循面向对象思想的健壮的way应用程序，可以选择JSP+(只要您不像90年代那样使用在其中嵌入原始的Java代码)。|1258699|XML和RDBMS都是存储数据的方法。然而，RDBMS提供了使用SQL作为语言来选择和操作特定数据的能力，这可以比使用XML的效率高得多。|1258700|将JSP%2BXML与PHP%2BMySQL进行比较有点像将苹果与橙子进行比较。然而，作为一种数据存储，XML给了您更多的好处，所以您实际上更喜欢MySQL，“尽管”它与PHP一起使用。但是，您可以像使用Java一样访问数据库。首先，这里有用于的JDBC+API。总而言之，我更喜欢JSP%2BSQL。|offset|length|1258701|1258702|我知道JSP可以使用Java，但我觉得它与HTML的关系更“自然”，而且还具有动态类型的优点，而且应用范围更广、需求更广。这是有原因的吗？|1258703|1258704|1258705|对于对编程一无所知的人来说，这是最容易上手的。你所需要的只是一个简单的and服务器和一个文本编辑器。使用PHP开发它非常快，因为它具有即时反馈，并且在web上有无数的教程和代码片段可用。此外，您还可以选择更多的免费PHP虚拟主机，而您必须为可靠的JSP/Servlet主机支付更多的费用。|1258706|entityMap|0|LINK|mutability|MUTABLE|url|http://download.oracle.com/javase/tutorial/jdbc/basics/index.html^0|0|0|0|0|0|0|0|3B|8|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|15|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|16|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|18|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|19|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|1A|7|@]|8|@]|9|$]]|$1|L|3|M|4|5|6|1B|7|@]|8|@$N|1C|O|1D|1|1E]]|9|$]]|$1|P|3|-4|4|5|6|1F|7|@]|8|@]|9|$]]|$1|Q|3|R|4|C|6|1G|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|1H|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|1I|7|@]|8|@]|9|$]]|$1|U|3|V|4|5|6|1J|7|@]|8|@]|9|$]]|$1|W|3|-4|4|5|6|1K|7|@]|8|@]|9|$]]]|X|$Y|$4|Z|10|11|9|$12|13]]]]

<blockquote>
 I have a lightweight online shopping site based on JSP and XML, and I'm wondering what the particular weaknesses of this system are as opposed to, say, PHP and MySQL?
</blockquote>

JSP and PHP are both view technologies. JSP has the advantage of being backed by Java (EE) which is a strong language and platform. PHP has the advantage of being the easiest and most public adoptable web programming language ever. The disadvantages speaks for itself.

To develop a robust webapplication following the OO ideology, pick JSP (as long as you don't embed raw Java code in it the '90s way using <a href="https://stackoverflow.com/questions/3177733/howto-avoid-java-code-in-jsp-files">scriptlets</a>). If you're in a hurry and/or don't care about future maintainability and want to develop an e-commerce website in one day, then pick PHP.

XML and RDBMS are both ways to store data. RDBMS in turn, however, offers the ability to use SQL as language to select and manipulate specific data which can be done tremendously much more efficient than ever possible with XML.

Comparing JSP+XML with PHP+MySQL is a bit like comparing apples with oranges. XML however bites you much more as being a data store, so you would really prefer MySQL "in spite of" that it goes with PHP. You can however access databases as good with Java. To start, there you have the <a href="http://download.oracle.com/javase/tutorial/jdbc/basics/index.html" rel="nofollow noreferrer">JDBC API</a> for. All with all, I'd prefer JSP+SQL.

<blockquote>
 I know JSP can use Java APIs, but I feel PHP has a more "natural" relationship with HTML and also has the benefits of being dynamically typed, and is far more widespread and in-demand. Is there a reason for this?
</blockquote>

It's the most easy to pickup by ones knowing absolutely nothing about programming. All you need to have is a simple webserver and a texteditor. It's very fast to develop with PHP as it has instant feedback and there are countless tutorials and code snippets available on the web. Further you have also much more choice of free PHP web hosting while you have to pay a bit more for a solid JSP/Servlet hosting.

blocks|key|784461|text|如果您希望在实体之间建立关系，那么我发现XML比关系数据库更难使用。确定存在的关系不仅会导致问题(需要在内存中维护这些关系的映射，或者需要重复读取大量文件)，而且使用XML维护引用完整性也是一件非常痛苦的事情。甚至像根据某种分类对物品进行分类这样简单的事情(X是割草机是一种户外设备是一种...)这将成为XML的一个问题，因为您必须开发一些外部工具来确保使用一致的词汇表。对于RDBMS，您只有一个术语表，其中包含父ID和子ID。商店中的任何项目都可以引用分类法ID。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|784462|当我试图用XML做太多事情时，我发现自己用一堆草率的外部工具重新创建了RDBMS的一些最有用的特性。|784463|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|$]]

If you are in a situation where you anticipate having relationships between entities, I have found XML to be significantly more difficult to work with than a relationship database. Not only does determining what relationships exist cause problems (requiring you to either maintain a map of these relationships in memory or to read in large sets of files repeatedly), but maintaining referential integrity is a terrible pain with XML. Even something as simple as classifying items according to some taxonomy (X is a lawnmower is a kind of outdoor equipment is a kind of...) becomes a problem with XML, as you will have to develop some external tools to ensure that you are using a consistent vocabulary. With a RDBMS, you just have a table of terms which have parent and children IDs. Any item in the store can just refer to the taxonomy IDs.

When I have have tried to do too much with XML, I've found myself crudely recreating some of the most useful features of an RDBMS with a sloppy collection of external tools.

blocks|key|4003202|text|使用XML作为电子商务的数据存储并不常见，因为存在性能问题，而且(我的)SQL运行得很好。如果您想尝试一些新的东西，可以用MySQL交换XML。我看不到改变编程语言有什么真正的好处，事实上，我认为如果你改变语言，你会注意到生产率的显著下降。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4003203|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|$]]

Using XML as data storage for a e-commerce isn't that usual because of performance issues and, well, because (My)SQL works so well. If you want to try something new, swap XML with MySQL. I don't see any real benefits with changing the programming language, in fact, I think you'll notice a significant productivity dip if you change languages.

blocks|key|4848619|text|相关，但离题:你说的是“轻量级”吗？在这种情况下，sqlite可以同时击败XML和数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4848620|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|$]]

Related, but off topic: did you say "lightweight"? in that case, sqlite could beat both XML and Database..

blocks|key|4848723|text|如果只存储事务性数据，那么就没有任何RDB不能解决的问题。但是，如果您的数据更多地面向文档(更混乱)，那么您可能希望查看几个原生xml及其XQuery接口中的任何一个。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4848724|eXist、Documentum+xDB、甲骨文伯克利、MarkLogic+(大公司)只是其中的一小部分。您可能还会对http://en.wikibooks.org/wiki/XRX感兴趣|offset|length|4848725|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikibooks.org/wiki/XRX^0|0|1N|W|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

If you're storing only transactional data you don't have any problems that an RDB would not solve. But if your data is more document-oriented (messier), you may want to look at any of several native xml DBs and their XQuery interfaces.

eXist, Documentum xDB, Oracle Berkeley, MarkLogic (for big stuff) are just a few. You might also be interested in <a href="http://en.wikibooks.org/wiki/XRX" rel="nofollow noreferrer">http://en.wikibooks.org/wiki/XRX</a>

blocks|key|4848747|text|从另一个角度来看，您可以在couchdb中查看json。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4848748|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|$]]

On a different tack, you could look at json in couchdb.

I have a lightweight online shopping site based on JSP and XML, and I'm wondering what the particular weaknesses of this system are as opposed to, say, PHP and MySQL?

I know JSP can use Java APIs, but I feel PHP has a more "natural" relationship with HTML and also has the benefits of being dynamically typed, and is far more widespread and in-demand. Is there a reason for this?

Benefits of databases as opposed to XML in a lightweight shopping site?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个基于JSP和XML的轻量级在线购物网站，我想知道这个系统相对于PHP和MySQL有什么特别的弱点？我知道JSP可以使用Java API，但我觉得PHP与HTML的关系更“自然”，而且还具有动态类型的优点，而且使用范围更广、需求更广。这是有原因的吗？

问在轻量级购物网站中，数据库相对于XML的优势是什么？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在轻量级购物网站中，数据库相对于XML的优势是什么？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在轻量级购物网站中，数据库相对于XML的优势是什么？
EN