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 24, 2008
In this interview made by Sadek Drobi during QCon San Francisco 2007, Neal Ford talks about the tendency of having multiple languages running on one of the two major platforms existing today: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
Watch: Neal Ford On Programming Languages and Platforms (32 min)
Neal talks about the need of developing languages, like Ruby and Groovy, to run on top of the JVM due to limitations of the Java language. Ruby, he says, is a powerful dynamic language offering the programmer the ability to write cool stuff in simple ways, giving him more flexibility and increasing his productivity.
Neal also talks a lot about meta-programming. He notices the limited meta-programming features existing in Java, and makes a case for the meta-programming support existing in Ruby.
Neal thinks that in the next decade, we will see several, some of them specialized, languages running on the most prominent platforms existing today, Java and .NET. This combination of languages-platforms allow the developers to choose the most efficient language for a specific task while not having to worry about deploying the resulting code since it runs on well tested and proven platforms.
I have heard Neal Ford use the term "priesthood" in one or two of his talks. I'm sure he meant that instead of "pre-stood" as transcribed above.
"it was trying to be backwards compatible with C and C++ to attract members that pre-stood." should be "it was trying to be backwards compatible with C and C++ to attract members *of* that *priesthood*."
Should be called, Why you should switch to Ruby from Java!
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.
2 comments
Watch Thread Reply