If I remember right, this joke is also told in the Hollywood drug-flick "Traffic", from 2000 or so. In the movie, the burnt-out drug czar of the old US administration mentions this joke to his ambitious successor, played by Michael Douglas.
You are wrong here. "The 7 Habits of Highly Effective People" is by Steven Covey. However, she said her favorite writer of management books is Peter Drucker, who described "Seven Sources of Innovation" http://snakecoffee.wordpress.com/2006/04/30/peter-druckers-s..., praising Japanese companies
Your post is so wrong that it is almost trolling. Just some counterexamples.
The Fukushima Mark-1 reactors are of very dangerous design, and that is well-known. (For example their containment is perforated at key positions, by design)
Ambient radioactivity is so high in central Japan that it should definitely be considered a hazard (just search on Youtube for Japanese people filming themselves walking around with Geiger counters and measuring the signal, e.g Youtube user "Chanbukimi"). Government ignores it or plays it down.
Exremely radioactive "radiotrophic funghus" (see Wikipedia) is everywhere in the Fukushima area and even in Tokyo.
Cancer risks by long-term low-dose radioactive exposure are even higher than estimated by the models promoted by governmental regulatory bodies. Risks are higher for children and women in particular, and simple back of the envelope calculations can show this convincingly (to me, that is).
The whole food chain in Japan is messed up for the foreseeable future, and this holds for Pacific seafood as well. Young Tuna fish catched in the San Diego area are slightly radioactive, although these fish are so young that they could not have stayed in radioactive seawater near Japan for more than a couple of months, and they are still contaminated.
There is much more contamination to come as the radioactivity spreads just by natural mass transfer processes (water cycle, carbon cycle).
in Germany : Chemnitz Linux Days / Chemnitzer Linux Tage. Happen usually on a weekend in March. Entrance fee is 8 Euros. Great value, very nerdy, never sold out,
You are correct, in order to use a public data set you will have to create an EBS volume with the corresponding snapshot and attach it to an instance. There is currently no option for read-only access.
What do you think about "grid computing" concepts? Are they too academic? outdated? more/less general? Is your architecture a different approach or just a variation on the theme, a special case?
Technically, the architecture promoted in the book is "grid computing" -- that is, a fully distributed set of resources that work together to accomplish a common task.
Many commercial grid computing products try to be all in one -- that is, handle storage and computation. They don't apply to every problem because they only have one kind of storage meant for certain kinds of tasks.
The architecture in Big Data is a general-purpose way to compute arbitrary functions on arbitrary data, at scale and in realtime. Every data problem you'd ever want to do can be described as a function on data, which is why this architecture is so general-purpose. I recommend reading Chapter 1 in the book (which is free to download from the webpage for the book) where we explain these ideas much further.
Will there be a chapter about how your preferred architecture compares to in-memory databases technologies? SAP has been creating a lot of marketing hype on this in the last years. Indeed I think a lot of business problems can be solved by cramming more RAM into centralized servers. Yesterday's big-data problems are now routine if you have a dozens-of gigabytes of RAM machine available.
Or is this question not applicable at all (because the architecture makes no assumptions on the type of data storage); the requirements and usage scenarios are completely different?
The architecture described in the book is fully distributed and horizontally scalable, and I won't be looking at scale-up techniques. The chapters on Storm and distributed RPC does have an emphasis on using lots of RAM for certain tasks though by partitioning data appropriately across the nodes.
I brought Sam on as a co-author at the 1/3 mark of the book (when Manning does the first round of reviews). So far Sam has helped with the revisions necessary to go from review -> MEAP, and we'll be splitting up the future chapters.
>(Consider "I don't know if I learned anything from them. " Footnote: 1 "In practice formal logic is not much use,..." )
This guy has programmed massive amounts of LISP code, and written books about LISP.
How can he say that his training in formal logic didn't take him anywhere?