News for hackers. Stuff that matters.
Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by pwittrock on Tuesday February 19, 2013 @12:01PM (#5245406)
fwiw: there is a pretty cool paper on abstractions over mapreduce to make life simpler: http://dl.acm.org/citation.cfm?id=1806638
Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by dsl on Tuesday February 19, 2013 @11:19AM (#5245057)
Go is awesome. :)
Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by perryg on Tuesday February 19, 2013 @11:05AM (#5244969)
Solid write up. What were the advantages/disadvantages to writing a DB engine in Golang vs C++ or Java
Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by voidlogic on Tuesday February 19, 2013 @11:10AM (#5244998)
Both Go and Java are more likely going to have a faster development cycle for many developers than C++ and are less likely to have memory management bugs because they are garbage collected and memory safe[1]. Compared to many languages like Ruby, Python, etc all three of those are "high performance" languages. With a lot of optimization C++ has the potential to probably be the "fastest" solution. It all comes down to balancing execution performance, memory efficiency and development maintenance efforts.

While Go is a young language, I find working in it to be extremely productive, it makes concurrency easy to implement and get right, and produces application with good run-time characteristics.

[1]: http://en.wikipedia.org/wiki/Memory_safe

Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by joshfraser on Tuesday February 19, 2013 @11:10AM (#5244999)
In general, Golang lets you code at higher level without compromising performance.
Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by wookietrader on Tuesday February 19, 2013 @01:31PM (#5246072)
ATLAS is a very bad name to pick; it's already taken when it comes to numerical data processing.
Re:Big Wins Processing Big Data: Behind the Scenes with Big ... by voidlogic on Tuesday February 19, 2013 @01:43PM (#5246166)
It is just an internal project name. If we open source the map reduce library we can always rename it.