GAE DataStore与谷歌云SQL企业管理系统 [英] GAE DataStore vs Google Cloud SQL for Enterprise Managment Systems

问题描述

我正在构建一个使用gae的企业管理系统的应用程序。我已经使用gae和数据存储构建了多个应用程序，但从未需要大量用户输入事务以及管理和管理报告。我最担心的是，当我需要创建交叉表和其他详细报告（或商业智能报告和数据处理）时，我将面临gae的数据存储区查询和数据拉取限制问题。在过去，我已经构建了使用C ++ / c＃/ Java针对Oracle / MySql / MSSql的系统（其中包含为了在复杂的或频繁访问的数据库结果上增加一些性能，一个缓存层被加入了）。

我一直在阅读，我们抛弃了旧关系数据的思想，到天空中的大麦克哈特表的新世界......但新的并不总是更好......任何有关上述的洞察力或经验将是有益的。

解决方案

从云端SQL常见问题解答：

我应该使用Google Cloud SQL还是App Engine Datastore？

这取决于应用程序的要求。 Datastore提供高度可扩展的NoSQL键值>存储，但不支持SQL数据库提供的复杂查询。 Cloud SQL支持复杂查询和ACID事务，但这意味着数据库充当固定管道，性能的可伸缩性较差。许多应用程序使用这两种类型的存储。

如果需要大量写入（〜XXX每秒）分布式密钥，这就是Google App Engine数据存储真正闪耀的地方。

如果您需要支持复杂和随机的用户制作查询，那么Google Cloud SQL更方便。 / p>

I am building an application that is an enterprise management system using gae. I have built several applications using gae and the datastore, but never one that will require a high volume of users entering transactions along with the need for administrative and management reporting. My biggest fear is that when I need to create cross-tab and other detailed reports (or business intelligence reporting and data manipulation) I will be facing a mountain of problems with gae's datastore querying and data pull limits. Is it really just architectural preference or are there quantitative concerns here?

In the past I have built systems using C++/c#/Java against an Oracle/MySql/MSSql (with a caching layer sprinkled in for some added performance on complex or frequently accessed db results).

I keep reading that we are to throw away the old mentality of relational data and move to the new world of the big McHashTable in the sky... but new isnt always better... Any insight or experience on the above would be helpful.

解决方案

From the Cloud SQL FAQ:

Should I use Google Cloud SQL or the App Engine Datastore?

This depends on the requirements of the application. Datastore provides NoSQL key-value > storage that is highly scalable, but does not support the complex queries offered by a SQL database. Cloud SQL supports complex queries and ACID transactions, but this means the database acts as a ‘fixed pipe’ and performance is less scalable. Many applications use both types of storage.

If you need a lot of writes (~XXX per/s) to db entity w/ distributed keys, that's where the Google App Engine datastore really shine.

If you need support for complex and random user crafted queries, that's where Google Cloud SQL is more convenient.

这篇关于GAE DataStore与谷歌云SQL企业管理系统的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！