开始Cassandra - 使用Kundera？还有什么？ [英] Beginning Cassandra -- Use Kundera? Something else?

问题描述

我们正在用Cassandra弄湿我们的脚。我们没有任何经验，这个特定的平台，但有经验的开发人员与JavaEE，JPA等。我遇到了Kundera库，提供了一个JPA实现兼容几个NoSQL数据存储，包括Cassandra。

We are in the process of getting our feet wet with Cassandra. None of us have any experience with this particular platform, but are experienced developers with JavaEE, JPA, etc. I came across the Kundera library that provides a JPA implementation compatible with several NoSQL datastores, including Cassandra.

沿着这条路线走下去是很诱人的，因为我们能够更快地开始跑步。然而，这是正确的想法吗？使用这样的库有什么折衷？它如何影响性能？是否有巨大的区别？

It's tempting to go down this route, as we will be able to get up and running MUCH faster. However, is it the right idea? What are the tradeoffs of using a library like this? How does it affect performance? Is there a huge difference?

我很想知道别人使用这个库的经验。

I'm curious to know what experiences others have had using this library. And, if there is something else we should look at instead I'd love to hear about it.

推荐答案

选择Jonathan的（jbellis ）到下一级，IMHO，像hibernate或JPA规范的ORM的目的是隐藏SQL的复杂性，因为应用程序开发人员在对象而不是SQL中处理最好。
类似地，kundera隐藏了NoSQL的复杂性，但是以一种智能的方式，它允许它使用NoSQL的力量，但仍然使开发人员更容易使用传统的RDBMS范式。
然而，正如Jonathan所提到的，你应该仍然理解Cassandra数据建模的概念，否则，你将最终创建另一个SQL像怪物，甚至在Cassandra。
Kundera通过使用优化技术（例如嵌入式或一对多关系）自动转换为多个列而不是创建新的Columnfamilies（RDBMS表等效项），从而避免创建物理关系模型，从而有助于此NoSQL建模。
一个工具只有工匠/使用它的女人的技能才好！

Taking Jonathan's (jbellis) to the next level, IMHO, the purpose of ORMs like hibernate or JPA specs is to hide the complexities of SQL since Application developers deal best in objects and not SQL. Similarly, kundera hides the complexities of NoSQL but in an intelligent way that allows it to use the power of NoSQL but still make it easy for developers to use the traditional RDBMS paradigm. However, as Jonathan mentions, you should still understand Cassandra data modeling concepts, otherwise, you will end up creating another SQL like monster even over Cassandra. Kundera does help in this NoSQL modeling by using optimization techniques such as Embedded or One-to-Many relationships automatically converted into multiple Columns rather than creating new Columnfamilies (RDBMS tables equivalents) thus circumventing creating a physical relational model. "A tool is only as good as the skills of the craftsman/woman using it!"

这篇关于开始Cassandra - 使用Kundera？还有什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！