You’ve probably read about the central goals of YARN and seen the architecture of YARN, but it’s worth having as many details about it as possible:
A key paragraph in Arun Murthy’s post about Apache Hadoop YARN:
MapReduce is great for many applications, but not everything; other programming models better serve requirements such graph processing (Google Pregel / Apache Giraph) and iterative modeling (MPI). When all the data in the enterprise is already available in Hadoop HDFS, multiple paths for processing data is critical.
That’s for all the critiques Hadoop is getting.
Original title and link: The Future of Hadoop: YARN Explained ( ©myNoSQL)