blocks|key|4436367|text|当数据库事务数增加时，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436368|性能。|blockquote|4436369|4436370|4436371|不是Django的问题，真的。|4436372|通过Apache和mod_wsgi，你可以有很多并发的Django会话。所有这些都将共享一个公共数据库。|4436373|因此，这完全是一个数据库问题。您应该能够配置足够的Apache/Django会话，使您的数据库不堪重负。|4436374|包含在|4436375|中的Django+OR映射是一个很好的选择，或者我应该实现它们。|4436376|4436377|4436378|是。这是一个非常好的选择。|4436379|在你能用证明是你的瓶颈之前，使用它。|offset|length|style|BOLD|4436380|当您向上扩展时，您将重新处理数据库、缓存和其他体系结构特性。因为ORM有一个缓存(就像你的数据库一样)，所以在这里你很少遇到性能问题。|4436381|你可以的。|4436382|但是您的大多数性能问题将是通过Apache下载静态媒体文件。|4436383|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|4|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1K|8|@$W|1L|X|1M|Y|Z]]|9|@]|A|$]]|$1|10|3|11|5|6|7|1N|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1O|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1P|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|17|$]]

<blockquote>
 performace when number of DB transactions increases.
</blockquote>

Not a Django problem, really.

You can have a lot of concurrent Django sessions via Apache and mod_wsgi. All of them will share a common database.

Therefore, this is entirely a database problem. You should be able to configure enough Apache/Django sessions that your database is swamped.

<blockquote>
 OR Mapping included inside Django is a good choice or should I implement them.
</blockquote>

Yes. It's a really good choice.

Until you can prove that the ORM is your bottleneck, use it.

As you scale up, you will rework your database, your cache, and other architectural features. Since the ORM has a cache (as does your database), you rarely have performance issues here. 

You can.

But most of your performance problems will be downloading static media files through Apache.

blocks|key|3026455|text|我应该补充的是，在使用Django+ORM时，企业应用程序可能会遇到的一个大问题是，它的能力受到一定程度的限制(即它可以表达的查询)。我认为如果你做两件事，这是可以处理的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3026456|3026457|致力于尽可能多地在Django+ORM中表达查询(如果没有经验，很容易就会认为查询在Django中是不可能的)。|ordered-list-item|3026458|如果在django中查询真的是不可能的(如果你真的不确定，也可以问IRC+#django频道或django-users组)，将查询存储在您的数据库管理员可以管理或查看的queries.py文件中。(它可以是模型文件引用的平面字典。)|3026459|3026460|作为第二点的一个例子:你没有理由不能编写一个查询存储管理器，它的用法如下:假设你有一个名为blog的应用程序，它有一个名为Entry的模型：|3026461|#+models.py
class+Entry(models.Model):
++++objects+=+project.QueryStorageManager()
++++author+=+models.ForeignKey(User)
++++body+=+models.TextField()
++++slug+=+models.CharField(max_length=512)
++++published_date+=+models.DateField()

++++@project.StoredQuery("getEntryMonthHistogram")
++++def+getEntryMonthHistogram(self,+sql,+author):
++++++++return+objects.runQuery(sql,+author)

#+queries.py
{
"getEntryMonthHistogram":+"""SELECT+EXTRACT(MONTH+FROM+published_date),
++++++++++++++++++++++++++++++++++++REPEAT('*',+count(*))+histogram
+++++++++++++++++++++++++++++FROM+++blogs_entry
+++++++++++++++++++++++++++++WHERE++author_id+=+%25s""",|code-block|syntax|javascript|3026462|}|3026463|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|W|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|Z|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|10|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|S|$]]

I should add that one big issue that enterprise applications may have when using the Django ORM is that it is somewhat limited in its capability (i.e. what queries it can express). I think this is manageable if you do two things:

<ol>
<li>Strive to express queries in the Django ORM as much as possible (without experience it may be too easy to dismiss a query as not possible in Django).</li>
<li>If the query is really impossible in Django (you can also ask the IRC #django channel or the django-users group if you are really unsure), store the query in a queries.py file that your dba's can manage or look at. (It can be a flat dictionary referenced by your models file.)</li>
</ol>

As an example of point 2: There's no reason you can't write a query storage manager that's used in the following way: Suppose you had an app named blogs with a model called Entry:

<pre><code># models.py
class Entry(models.Model):
 objects = project.QueryStorageManager()
 author = models.ForeignKey(User)
 body = models.TextField()
 slug = models.CharField(max_length=512)
 published_date = models.DateField()

 @project.StoredQuery("getEntryMonthHistogram")
 def getEntryMonthHistogram(self, sql, author):
 return objects.runQuery(sql, author)

# queries.py
{
"getEntryMonthHistogram": """SELECT EXTRACT(MONTH FROM published_date),
 REPEAT('*', count(*)) histogram
 FROM blogs_entry
 WHERE author_id = %s""",
</code></pre>

}

blocks|key|1030431|text|我的公司刚刚为一个基于Django的大型企业构建了这样一个系统，包括所有的移动系统。有了django，开发成本很低，企业服务器堆栈内部的可运行性也不成问题。甚至Django也设法让我们通过了渗透和安全测试。如果使用任何其他语言，在极端的预算限制下，我们都不可能成功完成这个项目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1030432|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|$]]

My company did just build such a system for a large scale enterprise based on Django including all mobile systems. With django the dev cost were low and runnability inside enterprise server stack was no problem. Even Django managed to let us pass the penetration and security test. with any other language we would not have been able to succeed with this project under extrem budget restrictions

I wanted to know is Django a good choice for a big web applicatin(Social Network)? More specifically, I need some suggestion on performace when number of DB transactions increases and I want to know is the embedded OR Mapping included inside Django is a good choice or should I implement them.

Thanks

Django for enterprise web application

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我想知道Django是一个大型web应用(社交网络)的好选择吗？更具体地说，当DB事务数量增加时，我需要一些关于性能的建议，我想知道包含在Django中的嵌入式OR映射是一个很好的选择，还是应该实现它们。谢谢

问用于企业web应用程序的Django
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于企业web应用程序的DjangoEN