The article is from 2013, so its very much likely that some of the issues has been handled by MongoDB itself or some agreed practices.