Also, how does this work in the presence of replicas? Does every replica go through the strategy? What if one or more replicas go down during a transaction?
2,343 karma · joined January 17, 2009
Also, how does this work in the presence of replicas? Does every replica go through the strategy? What if one or more replicas go down during a transaction?
Main use case: Multi-threaded low latency data access. It is optimized for use cases where the insert/update rate is very high. In short, it has an LSM tree to quickly add new/updated records. At frequent intervals this LSM tree is merged into the on-disk pages. It is very well engineered, making the lookups very fast as well.
Queries can touch data on disk as well.
Rocks is an embedded database. Natively written in C++, but has bindings for other languages. [2]
No, nodes do not talk to each other.
Something I am personally excited about: RocksDB has a merge operator, which is (probably) still in development. It allows you to update the value of an entry by providing a merge function. It is extremely useful to merge data if you binary format supports it (for example, protobufs do this natively, and it will be very smart to store your protobuf binary natively in Rocks, and do regular merges to it).
No, an in-memory dictionary will provide far fewer guarantees and features.
[2] https://github.com/facebook/rocksdb/wiki/Third-party-languag...
Document everything you see. Take a good camera with you, and if you don't know how to use an SLR, this is the perfect time to learn some basic tricks. Once you pick a camera, you can find some tutorial on the web, which teaches you the basics for that brand/model.
I would use this time out to "take a break" from computer science. But if you can't stay away from it, pick up a book like SICP (http://mitpress.mit.edu/sicp/). This is one of those books which you want to read away from all distractions and think deeply about. If you can, download the accompanying video lectures:
http://ocw.mit.edu/courses/electrical-engineering-and-comput...
X.getA().getB().getC().getD()
we have to X.flatMap(X::getA)
.flatMap(X::getB)
.map(X::getC)
.orElse("UNKNOWN"); //[1]
Not sure why this is going to be better?[1] http://www.oracle.com/technetwork/articles/java/java8-option...
My idea of a grand future is when we can travel across the globe in less than hour, and pay less than $50 doing it.
In the United States probably. The author doesn't sound too old, and says that he/she got access to the internet much later. Which means the author is probably from the Middle east or China or South Asia. The work culture there is not as open as in the west. Daily job means monotonous routine work. What excited him about the prime numbers problem was the novel aspect of it, and the fact that he was in control. Later, in his/her day job, that was no longer the case -- someone else was making the decisions. Until these nuances trickle into daily jobs, most people will sooner than later burnout.
Its maybe because I'm new to the language, but I have to add 'lang' to all my Google searches for Go documentation/tips, otherwise the keywords are almost always misinterpreted.
[1] http://www.infoq.com/presentations/Design-Composition-Perfor...
[1] http://www.valorebooks.com/textbooks/automata-theory-and-app...
BTW, all the best with your website. Hope you take more avatars "where go where no man has gone before!"
1. If photos have a hashtag, display it alongside an image. Text is the underestimated medium of non-personal image interpretation. Especially, when the data rate is so high, there needs to be some more precise clue about what the images are actually trying to convey.
2. Aggregate photos with similar intent. Group them into a box or color code their borders. Many tweets have GPS tags. Use them to provide a map interface to either filter some or just add a tag indicating the place of origin.
3. Most people who can only read 2-3 languages, and tweets in other languages will be treated as noise, no matter how relevant. The only alternative is combine them with a similar tweet in a language the user can understand.
4. Is there any reason photos change randomly across cells, and not in any order (as compared to say raster scanning the table and replacing photos)? Personally think that changing photos in some order is less painful on the eyes. I get the feeling that I am missing out an a lot of content because of this. Maybe replace only one section of the table at at time?
Good luck!