New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Aug 14, 2008
In this presentation made during Agile 2008, Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, Chief Engineer at Toyota, and the lessons he learned from him.
Watch: The Development of a New Car at Toyota (25 min)
Kenji met Nobuaki Katayama during Developers' Summit 2008 in Tokyo where Toyota's Chief Engineer kept a presentation about the process used in creating a new car. Nobuaki says there are three main phases in car development:
Nobuaki emphasizes the first phase, creating a good concept being the most important. A complete concept is created, then it is tested with dealers and possible customers around the country to see if the concept is well received. Then comes prototyping and production.
Nobuaki gives some advices useful in software development. One of them is honest communication. Another, face-to-face communication, or TV conference if face-to-face is not possible. Another is: "Don't complain. Cooperate", and is Toyota's DNA, according to Nobuaki.
Nobuaki also noted some differences between Agile methodologies and car manufacturing ones. For example, there is no room for repetition or iteration when making a car.
Transforming Software Delivery: An IBM Rational Case Study
SCM best practices for multiple processes, releases & distributed teams
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
It's interesting how the CE prefers to have a non-Charismatic leader for teams. That was about the only surprise. The 'Toyota Way' is usually always the focus, but I would be surprised if every Japanese car manufacturer shared these values and perception of leadership.
Honda, for example, probably has a different value system - it seems that passion & charisma are positive aspects in that system. Take Formula 1 for example - both manufacturers have had long stints but Honda clearly has the edge when it comes to World Championships and race wins (5 championships, 71 wins as an engine supplier, 3 Factory wins).
Toyota, if I remember correctly, has yet to register a race win in 116 attempts with a yearly budget rumored to be in the $200-600M zone. More alarmingly, Toyota hasn't shown itself to be particularly accepting of their F1 shortcomings, neither are they taking any calculated risks. They have repeated, refined and spiraled-up to nowhere. ;)
So, the question that sprung up in my mind is the following:
In a system that has a low tolerance for passion & charisma, can adversity & chaos be easily overcome when encountered? Or would a company that encourages passion & charisma respond & overcome those challenges better?
It is no surprise to me that while GM/Toyota/Ford saw U.S. domestic sales slump, Honda somehow conjured up a sales gain in the first seven months of 2008 (source: Reuters).
Must have been some charismatic leader who spurred them on.
Cheers,
Zubin Wadia
CTO
www.zwadia.com
www.imagework.com
"Business Acceleration through Process Automation."
I think what ever you do, you always have to have a sense of balance. Charisma and passion can be good things but they can also take you to a very bad place if you can not sit back and see the big picture in a calm and calculative manner.
I can understand why a more subdued and calm leader would be preferred in most situations. They can be wrong as anyone else, but it can be usually caught before things really go wrong. Charismatic leaders can be much harder to keep in check, as they usually carry so much unchallenged support by their own virtue that some natural feedback loops do not exist to correct failures in judgment.
I don't remember since I saw such a bad presentation. We all know how to read, the fellow was an extra... he should stayed mute.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
3 comments
Watch Thread Reply