Are we moving away from good "at scale" programming?
Watch the guy who talks a bit later. He works for disney and explains about his project called fastpipe that he developed addressing many of the concerns of modern day code usage of parrallelism.
He makes a lot of notions about how software developers are moving away from developing on their single developer machines and instead are getting a large headache from doing so by using node-based multicpu programming!
Hadoop is horribly inefficient at best it seems for it's overhead. And reliability seems to be becoming more and more of an issue.
He was able to achieve decent results computing using python which is known to be a slow language by finding good reliable ways of doing the parallel code development. He makes a lot of assumptions about reliability that also are very interesting decision wise that show that he has programmed for years.
I was wondering what other people think of some of the things he is saying. Are we moving away from the right decisions for developing parallel code?
It seems like we are getting away from the learning how to split things up into processes right without conflicts. And we don't really know how to always pick the more reliable code.
6 comments
[ 3.4 ms ] story [ 27.0 ms ] threadIf you have 100TB+ of data, you might need a cluster. Think about it, Google has to deal with all of the pages on the internet; pretty much no one else has that data. So why are we using their methodologies?
There are many people out there that can accomplish some of these tasks with better written code. There is also probably a need for a better hadoop. One that is less about clusters/multiple cpus and more about rented out bigger power computers.
In some ways the guy is probably blowing some steam, simply grabbing a bigger computer isn't always the best option, that's why clustered computing was even invented. I do think he has a point that people reach for it sooner than they need to. I've made that mistake before, and I just ended up settling for the pipeline approach.
If we focused harder on reliability and another service "like hadoop" would probably be created but for non-cluster/multicpu. And doing some of the decently sized tasks we would have better, faster, and more reliable tools at hand.
Maybe i'll try reddit in r/programming if I can't get more tommorrow.