About
All feedback (230)
- xe0199 (222)- Feedback left by buyer.Past monthVerified purchaseHope to deal with you again. Thank you.
- refurbifyllc (10546)- Feedback left by buyer.Past yearVerified purchaseThanks for the business!
- yun-573748 (1034)- Feedback left by buyer.More than a year agoVerified purchaseThank you for an easy, pleasant transaction. Excellent buyer. A++++++.
- mercisouthernlife (14444)- Feedback left by buyer.More than a year agoVerified purchaseThank you! If we didn't earn POSITIVE FB & 100% SATISFACTION, please contact us
- everythinggolf (23231)- Feedback left by buyer.More than a year agoVerified purchaseQuick response and fast payment. Perfect! THANKS!!
- adidas_official (624257)- Feedback left by buyer.More than a year agoVerified purchaseGood buyer, prompt payment, valued customer, highly recommended.~adidas_official
Reviews (4)
21 July 2013
Good product. Fast delivery.
Dharma Mittra is a truly great presence in yoga. His series is just what I needed to add something to my practice. This particular DVD (part 2) is definitely not for beginners though. He is also not so big on warm ups, so I add a few basic stretches to the beginning. That said, I LOVE THIS DVD. It has great time selections so you can do a 50ish minute practice, 70 or 85. Too many DVDs are only 30 minutes- not enough for serious yoga. This DVD is like having a real class at home. I highly recommend it.
07 July 2016
This is the best MINI box. Must have for oversea users.
This is the best MINI box. Must have for oversea users.
21 July 2013
Filled with information but not necessarily the information you want
I'm not a database person but I've worked with SQL databases (esp. MySQL) and have read a few papers about non-relational databases, particularly Google's Bigtable. I understand the "web-scale" data challenge and see how a distributed, fault-tolerant, tunable open-source database like Cassandra can be an incredibly useful tool for addressing it. Therefore I was really looking forward to the publication of Eben Hewitt's Cassandra, The Definitive Guide. I was hoping that it would lay out all the important things a person would need to know in order to decide whether Cassandra made sense for their project and, if it did, how specifically they would use it.
Now that the book's out and I've had a chance to read it once through, I have to say that it does not meet my expectations. The author is clearly very interested in his subject and also very anxious to share insights not only into Cassandra but into modern non-relational databases in general (to the extent of including a 25-page appendix "The Nonrelational Landscape" at the end of the book). He does a pretty good job of explaining how Cassandra works at the level of distributed storage including scaling as well as availability and consistency. And though I haven't gone through the steps, he seems to give pretty good instructions for installing, configuring and monitoring a Cassandra cluster.
What he doesn't cover nearly as well as I was hoping (and would have expected from an O'Reilly book) is data modeling in Cassandra and the actual APIs for putting data into the database and getting data out (i.e. querying). It's not that he doesn't cover these subjects at all. In fact he devotes two chapters to data modeling (Chapter 3 The Cassandra Data Model and Chapter 4 Sample Application) and two to APIs (Chapter 7 Reading and Writing Data and Chapter 8 Clients), and these chapters contain a lot of useful information. The problem is that the information I really want is either mixed in with other, for me, less important information and/or is too limited or even not present at all.
Here are some things that I would have expected to be presented in reasonably full, coherent form in a "definitive guide" to Cassandra:
Data modeling:
Column families, supercolumns and columns - what are they for, how do you use them effectively? Especially supercolumns, which, in conjunction with the intrinsically sparse data representation, allow you to blur the distinction between structure and data and store data in "wide" format and even as out-and-out row-specific lists. He touches on matters of this sort, including in the design patterns at the end of his Data Modeling chapter, but doesn't integrate them into a coherent account of how to use the Cassandra data representation model.
Lack of joins - what are the alternatives? He addresses this issue too, but mostly says, denormalize your tables and design for common queries - or even more bluntly, precompute the results of your common queries and put them into your database. This may be a good approach in some situations, but leaves a lot of questions like, when do you precompute your query results, where and how, what triggers the computation, and how do you handle data changes that invalidate previously precomputed query results (one of the problems that normalization and joins were originally designed to solve). Also, I believe he does not say very much about implementing joins and other complex queries on the client side. Does Cassandra have properties t