问题描述
我想了解数据库的可扩展性，所以我刚刚听说了一个关于高度可扩展的 Web 应用程序的习惯
I would like to understand database scalability so I've just heard a talk about Habits of Highly Scalable Web Applications
http://techportal.inviqa.com/2010/03/02/habits-of-highly-scalable-web-applications/
在这上面，主讲人主要讲的是关系型数据库的可扩展性.
On it, the presenter mainly talk about relational database scalability.
我还阅读了一些关于 MapReduce 和面向列的表、大表、超表等...试图了解哪些是最新的扩展 Web 应用程序数据的方法.但对我来说，第二组很难理解它适合哪里.
I also have read something about MapReduce and Column oriented tables, big tables, hypertable etc... trying to understand which are the most up to date methods to scale web application data. But the second group, to me, is being hard to understand where it fits.
它用作事务性的、可靠的数据存储?与否，它只是用于大型访问和处理以及处理我们将需要依赖 RDBMS 的细粒度操作?
It serves as transactional, reliable data store? or not, its just for large access and processing and to handle fine graned operations we will ever need to rely on RDBMSs?
有人可以对这些新技术及其使用方法进行全面介绍吗?
Could someone give a comprehensive landscape for those new technologies and how to use it?
推荐答案
基本上是关于使用正确的工具来完成工作.关系数据库已经存在了几十年，这意味着它们非常擅长解决当时没有改变的问题——例如跟踪销售情况.尽管它们已成为几乎所有事物的默认数据存储，但它们并不擅长处理 20 年前不存在的问题——尤其是可扩展性和没有明确定义、不变模式的数据.
Basically it's about using the right tool for the job. Relational databases have been around for decades, which means they are very good at solving the problems that haven't changed in that time - things like keeping track of sales for example. Although they have become the default data store for just about everything, they are not so good at handling the problems that didn't exist twenty years ago - particularly scalability and data without a clearly defined, unchanging schema.
NOSQL 是一类工具，旨在解决不完全适合关系数据库的问题.可扩展性是最广为人知的，尽管不太可能与大多数开发人员相关.我认为我们还没有看到的另一个关键用例是用于完全不需要担心数据存储特性的小项目，并且可以使用默认值 - 能够跳过数据库设计，ORM 和数据库维护是相当有吸引力的.
NOSQL is a class of tools designed to solve the problems that are not perfectly suited to relational databases. Scalability is the best known, though unlikely to be a relevant to most developers. I think the other key use case that we don't see so much of yet is for small projects that don't need to worry about the data storage characteristics at all, and can just use the default - being able to skip database design, ORM and database maintenance is quite attractive.
特别是对于电子商务，您最好至少部分使用 sql - 您可能使用 NOSQL 获取产品详细信息或推荐引擎，但您希望将销售数据放在易于查询的 sql 表中.
For Ecommerce specifically you're probably better off using sql at least in part - You might use NOSQL for product details or a recommendation engine, but you want your sales data in an easily queried sql table.
这篇关于“电子商务"可扩展数据库模型的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！