何时使用键值数据存储与更传统的关系数据库？ [英] When to use a key-value data store vs. a more traditional relational DB?

问题描述

何时通过关系数据库选择键值数据存储？什么考虑决定一个或另一个？什么时候混合的最好的路线？请提供示例。

解决方案

根据我的经验，如果你甚至提出是否使用传统vs做法，然后去传统。虽然神秘的做法是性感，有挑战性和有趣的，99.999％的应用程序呼吁一种传统的方法。

关于关系vs KV， 的问题是：

为什么我不想使用关系模型：...

因为你没有描述这个场景，任何人都不可能告诉你为什么不应该使用它。 KV的catch all原因是可扩展性，现在不是问题。你知道优化的规则吗？

1. 不要这样做。


KV是一种高度优化的可扩展性解决方案，将最多的可能对您的申请完全不必要。



When would one choose a key-value data store over a relational DB? What considerations go into deciding one or the other? When is mix of both the best route? Please provide examples if you can.

解决方案

In my experience, if you're even asking the question whether to use traditional vs esoteric practices, then go traditional. While esoteric practices are sexy, challenging, and fun, 99.999% of applications call for a traditional approach.

With regards to relational vs KV, the question you should be asking is:

Why would I not want to use a relational model for this scenario: ...

Since you have not described the scenario, it's impossible for anyone to tell you why you shouldn't use it. The "catch all" reason for KV is scalability, which isn't a problem now. Do you know the rules of optimization?

1. Don't do it.
2. (for experts only) Don't do it now.

KV is a highly optimized solution to scalability that will most likely be completely unecessary for your application.

这篇关于何时使用键值数据存储与更传统的关系数据库？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！