HNHacker News
TopNewBestAskShowJobs

alexpopescu

434 karma · joined April 6, 2009

submissionscomments
alexpopescu··on High performance real-time search, indexes store in Redis for Rails application
I could see such solutions used in cases where:

1. you are already using Redis for some other part of the application

2. you don't want yet to have Lucene/Solr/ElasticSearch

3. you don't need to support too advanced searches

On the other hand while building such a library could be a good learning exercise, I think that before using it in an application you should look for other already existing libraries and try to collaborate with the original authors.

--

All things NoSQL: http://nosql.mypopescu.com

alexpopescu··on Couchbase 2011 - Year in Review
> Not everything went as we hoped or expected, however. Unfortunately, we confused the heck out of many of our potential users. In addition to Membase Server and our new mobile products we also offered Couchbase Single Server which was a packaged “distribution” of Apache CouchDB. On top of that we began releasing developer previews of Couchbase Server 2.0, which incorporated CouchDB technology into Membase Server – but this product was not compatible with Couchbase Single Server (or CouchDB). If you are confused just reading this you get the point – and so do we.

Finally [1]

While the confusion started a long time ago [2], I would have thought that after the merge things would get simpler for the end users. But it took them another round of clearly spelled out messages from the community ([3], [4], [5]) to finally come out with a unified positioning.

Couchbase stepping away from offering a commercial version of CouchDB will allow others (probably Cloudant) to address any market needs. That's not to say that CouchDB needs the backing of a commercial entity, but sometimes having one helps with adoption in the "enterprisey" space.

[1]: This time used in the complete opposite sense of DaringFireball's usage of the word

[2]: http://nosql.mypopescu.com/post/1200041111/couchdb-revisited...

[3]: http://till.klampaeckel.de/blog/archives/174-Quo-vadis,-Couc...

[4]: http://nosql.mypopescu.com/post/12237740756/what-happened-to...

[5]: http://nosql.mypopescu.com/post/13569312049/couchdb-saga-clo...

alexpopescu··on It's Time to Drop the "F" Bomb - or "Lies, Damn Lies, and NoSQL."
That's not completely true. Take a look at Google's Megastore paper: http://www.cidrdb.org/cidr2011/Papers/CIDR11_Paper32.pdf

James Hamilton has a good summary of the ideas in the paper: http://perspectives.mvdirona.com/2011/01/09/GoogleMegastoreT...

alexpopescu··on Amazon Web Services are down
Instead of enumerating who's down, I'd be more interested to hear about those that survived the AWS failure. We could learn something from them.
alexpopescu··on Amazon Web Services are down
More comments coming from Adrian Cockcroft:

1. See slides 32-35 of http://www.slideshare.net/adrianco/netflix-in-the-cloud-2011

2. "Deploy in three AZ with no extra instances - target autoscale 30-60% util. You have 50% headroom for load spikes. Lose an AZ -> 90% util."

https://twitter.com/#!/adrianco/status/61089202229624832

alexpopescu··on CoSQL: SQL and noSQL are really just two sides of the same coin
@antirez as in any mathematical proof the most generic case is considered first. If X is a special case or is exposing special corner scenarios, I'd assume that could be covered by extension proofs.

I'm not saying Erik's article is bullet proof. But it offers a very interesting perspective on two data models that were considered conflicting.

alexpopescu··on The Redis Manifesto
Try to get that from the command line :-).
alexpopescu··on The Redis Manifesto
I suggest having a Redis command for it: redis man. Similar in a way to Python's import this
alexpopescu··on HBase 0.90.0 Released: Over 1000 Fixes and Improvements
There's an update on that from one commenter. He mentions that Hadoop 0.21 is not meant for production systems.
alexpopescu··on HBase 0.90.0 Released: Over 1000 Fixes and Improvements
Impressive release. And the first one as top Apache project. On the downside, unfortunately it's not compatible with the latest Hadoop, but there's a solution (not an app :) for that.
alexpopescu··on A NoSQL Community Effort
(Oops... I've managed to lose my initial comment.) Shortly, after writing about the NoSQL space for over 10 months, I've realized that putting together some good reference, structured materials about NoSQL databases and their case studies would be possible only with community's help.
alexpopescu··on MongoDB's lead developer: Foursquare outage post mortem
I didn't mean "wrong" in the full sense of the word. What I actually mean is that sharding based on user id will most probably not give/guarantee predictable distributions of the writes generated by users (basically there can be no guarantee that chunk#1 of users will always generate the aprox. same amount of data as chunk#2 of users).
alexpopescu··on MongoDB's lead developer: Foursquare outage post mortem
While the details are very interesting, there are still many questions to be answered (on both sides):

- how difficult would be to bring up read-only replicas? (hopefully that should take much less than 11 hours + 6hours) - why the 3rd shard could accommodate only 5% of the data? - how can you plan capacity when using the "wrong" sharding? (basically leading to unpredictable distributions)

I have posted the rest of the questions here: http://nosql.mypopescu.com/post/1265191137/foursquare-mongod... as I hope to get some more answers.

alexpopescu··on Two Reasons You Shouldn't Use MongoDB
I fail to see why analytics data seem to be considered "low quality" data ("we don't care if some stuff occasionally gets lost"). As far as I can tell, most businesses out there are driven by metrics which are derived from analytics data... so I don't agree that "it's OK to lose some".
alexpopescu··on CouchDB NoSQL Database Ready for Production Use
PR... sucks :(
alexpopescu··on Release: CouchDB 1.0 Finally Here
... and if I'm not mistaking, you can also get a free, hosted CouchDB account, thanks to Couch.io
alexpopescu··on Getting Started with NoSQL
Couple of weeks ago, I had the pleasure to sit down with Mathias Meyer, Chief Visionary at Scalarium, a Berlin startup and discuss NoSQL adoption. Like myself, Mathias is really excited about NoSQL and he uses every opportunity to introduce more people to the NoSQL space. The discussion has focused on how would someone start learning and using NoSQL databases and the path to follow in this new ecosystem
alexpopescu··on MongoDB Performance & Durability
Posted about this months ago: http://nosql.mypopescu.com/post/392868405/mongodb-durability...

I do agree durability is important, but as long as you are aware of this behavior and you consider it in your design, you may still find scenarios where the gained speed is a good trade off.

Another aspect that tends to be forgot when speaking about MongoDB is its fire-and-forget API. Combined with the behavior of automatic collection creation, innexistent data validation this may lead to "interesting" results.

alexpopescu··on Membase a new NoSQL
Interesting! I've concluded the same thing based on the very scarce info they're offering.
alexpopescu··on Reflections on MongoDB
> When should you use MongoDB? Always

NO, NO, NO. If you do that, then you’re definitely doing it wrong! Again! http://nosql.mypopescu.com/post/703837964/when-should-i-use-...

alexpopescu··on Scaling CouchDB
Indeed it's a bit brief... more of an overview. I'll definitely try to find some time to work on something more detailed.
alexpopescu··on Riak 0.11 released
Here is the description of a Riak cluster deployed on kiosks http://nosql.mypopescu.com/post/543171368/riak-in-production...
alexpopescu··on OrientDB: A new Open Source NoSQL DBMS
Other option may be BerkleyDB/Java. It should be pretty easy to get started. In terms of querying things may be a bit more difficult (as for any KV store), but as far as I remember there are ways to programmatically define secondary indexes. (note: I'm not affiliated with Oracle/Sun/Berkley/etc. :-)
alexpopescu··on Massive CouchDB Brain Dump
I totally agree. It sounds everyone is thinking that just because you can put anything inside your store that's also a good idea. And it definitely is not. I am trying to underline this quite often: http://nosql.mypopescu.com/post/507962068/the-role-of-data-m...
alexpopescu··on NoSQL Smackdown with Werner Vogels and MongoDB, CouchDB and Cassandra devs
Here are my notes and comments: http://nosql.mypopescu.com/post/459029585/nosql-smackdown-at...
alexpopescu··on MongoDB Durability: A Tradeoff to Be Aware Of
Would you mind expanding on this? I thought the role of the arbiter is to decide who's the master at one point in time. And while this is helpful for the whole coordination process, (by the way I think a similar effect could be achieved with smart clients) this impacts availability on not durability per se.
alexpopescu··on MongoDB Durability: A Tradeoff to Be Aware Of
It is my understanding that the arbiter is useful for the replica pair coordination, but that is not directly related to durability (i.e. the guarantee that once the user has been notified of success, the transaction will persist, and not be undone.)
alexpopescu··on MongoDB Durability: A Tradeoff to Be Aware Of
I think you are correct about the C and D. Considering replication is currently asynchronous it is clear that we cannot really talk about C.
alexpopescu··on MongoDB Durability: A Tradeoff to Be Aware Of
I don't think that any of the master/slave and the limited master/master replication are bringing any benefits to durability discussion. These both setups will behave exactly the same as the replica pair. The arbitrator server is an interesting option, but it has to deal with network partition and not durability. Such an arbitrator is not really useful for the replica pairs as these are self-managing the master-slave status.
alexpopescu··on MongoDB Durability: A Tradeoff to Be Aware Of
The tradeoff is giving up durability to performance. MongoDB operates under the assumption that durability is not critical and so will not write your data to disk. That allows it to perform at the speed of say memcached. For example CouchDB, which is another NoSQL solution in the same space of document stores, has durable writes (in fact it is ACID). You'll see a lot of benchmarks out there comparing these two (or MongoDB with MySQL) with the emphasize on the speed of MongoDB, while it would be more fair to benchmark MongoDB against memcached.
← PreviousPage 5 of 6Next →