什么是数据库的太大？ [英] What's TOO BIG for a database?

问题描述

我有一个好友为列出汽车销售的人运行网络应用程序。有几千个客户使用它，每个客户在数据库中有几百行，有时甚至几千行（有些已经打开了5年，每月有数百辆汽车销售，每个销售有10个行（注释，消息，等等））。他已经在一个物理服务器中的一个SQL Server数据库中运行此系统，具有类似20GB或RAM和几个处理器的全部时间，没有问题。这是一个奇迹吗？

I have a buddy who runs a web app for people listing cars for sale. There are a few thousand clients who use it, and each client has hundreds and sometimes thousands of rows in the database (some have been on for 5 years with hundreds of cars selling each month, and 10s of rows per sale (comments, messages, etc)). He has run this system in one SQL Server database in one physical server with like 20GB or RAM and a couple processors for the whole time, with no problems. Is this some sort of miracle?

就像大多数程序员一样，我没有DBA，只是得到，感谢ORMs等等。无论我在哪里，人们谈论需要为web应用程序的大用户分片或获取单独的数据库服务器。为什么是这样？有一个大的DB有很多或行真的是低效吗？

Just like most programmers, I'm no DBA and just get by, thanks to ORMs, etc. Everywhere I look, people talk about having the need to shard or get a separate database server for big users of a web app. Why is this? Is it really that inefficient to have a large DB with lots or rows? Should I plan to use Cassandra or something, or can I rely on scaling up well with Postgres?

推荐答案

我个人不打算使用Cassandra或其他东西认为你描述的是大数据库。服务器（20吉他的ram？;））听起来不错。它更多关于使用和设计。如果数据库被索引和设计良好，它可以在当前硬件上增长很多，大得多。

I personally don't think what you've described is that large of a database. The server (20 gigs of ram? ;)) sounds decent. It's more about usage and design. If the database is indexed and well designed, it can grow much, much larger on the current hardware.

在做任何类型的切换之前，我只需要查看归档无用的数据和优化查询，如果担心性能问题。

Before doing any sort of switch, I'd simply look at archiving useless data and optimising queries if there's a fear of performance issues.

这篇关于什么是数据库的太大？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！