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 Werner Schuster on Mar 03, 2008
* Enumerable#zip behavior reverted to 1.8 one. string
* Hash#flatten no longer work recursively.
Hash#flatten: I meanThere are also a few notable additions, such as
{a: [:a,1], b: 2}.flatten
to give
[:a, [:a, 1], :b, 2]
not
[:a, :a, 1, :b, 2]
as it used to.
Proc#curry, recently discussed here at InfoQ. Other additions: * Math.cbrt added.Adopters of Ruby 1.9 can use Multiruby to run tests on multiple Ruby versions to quickly determine changes in behavior.
* Math.{gamma,lgamma} added.
* import RubyGems r1601.
* Proc#curry added.
* Oniguruma 5.9.1
* added UTF-16,CP949,EUC-KR,GB12345,UCS-{2,4}{BE,LE},GBK,CP936,CP949, GB2312,UTF-7,BIG5,EUC-TW,GB18030,KOI8,KOI8-R,KOI8-U,Windows-1251 support.
A Guide to Branching and Merging Patterns
Agile Maturity Model Applied to Building and Releasing Software
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