News for hackers. Stuff that matters.
Re:Immutability, MVCC, and garbage collection (2013) by reitzensteinm on Saturday January 31, 2015 @10:39PM (#8979081)
I don't doubt that immutability in databases is expensive, but is anyone really arguing against that? The article seems like a straw man to me.

From watching Rich's talks on Datomic, the argument seems to be that for many problem domains, we can spend the cost of immutability to get a much nicer development environment.

If you're already sharding your DBs in a frantic effort to keep your web startup scaling, obviously switching to an immutable database is a bad idea.

But if you can fit every transaction your company has ever done in memory, why wouldn't you go append only?

While the latter might be a niche market today, if Moore's Law keeps up for another few decades it'll be the common case. I'm not clicking on more links than I was 15 years ago, but I've got three orders of magnitude more memory.

Re:Immutability, MVCC, and garbage collection (2013) by taeric on Saturday January 31, 2015 @11:34PM (#8979175)
Many of the arguments in favor of newer databases are about how much simpler these append only data structures make both storing and reasoning about things. The point of this article seems to be that this is neither absolutely true, nor new.
Re:Immutability, MVCC, and garbage collection (2013) by hyc_symas on Sunday February 01, 2015 @04:37AM (#8979554)
Agreed. None of the ideas are new, and append-only doesn't make life easier.