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 Peter Cooper on Nov 03, 2006
In 2001 Hal Fulton released The Ruby Way, only the second English language Ruby book available at the time. Since then Ruby has become popular in the West and with the help of Ruby on Rails has achieved significant critical success. With a significant number of enhancements and changes to the Ruby language and ecosystem of libraries and developers, Fulton decided a second edition was in order. That second edition of The Ruby Way, as published by Addison-Wesley, is now available.
For those unfamiliar with the first edition, The Ruby Way has a chapter for each major topic relating to Ruby with about ten to twenty sub sections each containing code examples of how to achieve a particular goal. Scanning through the contents pages is like scanning through a recipe book. Even though the book is not officially a "Ruby Recipes" book, it has a similar feel, with the added benefit that each code example demonstrates the most practical, and stylistically acceptable, route to a certain outcome.
The main topics the book covers are: Ruby concepts and syntax, strings, regular expressions, internationalization, math, dates and times, arrays, hashes and enumerables, data structures, I/O, metaprogramming, GUI development, threads, systems administration, data parsing, testing and debugging, distributing code, network programming, and the Web. Each section contains many 'recipes' and code samples.
With this cookbook style in mind, the book is not for beginners. Developers with experience of OOP could find the book useful to 'learn by example', but anyone unfamiliar with different languages, OOP and dynamic language features will find the book impractical to learn from. Fulton acknowledges this and squarely pitches the book at those who know at least a little Ruby but are looking for the way forward.
If you're not entirely convinced whether to buy the book or not, consider the kudos it has received from the highest echelons of the Ruby community. About the book, Rails creator David Heinemeier Hansson says, "Many of the early ideas for Rails were inspired by the first edition, especially what is now Chapter 11. It puts you on a roller coaster ride between 'How could I use this?' to 'This is so cool!' Once you get on that roller coaster, there's no turning back."
In the foreword, Matz talks about how he feels Fulton has come closest, in The Ruby Way, to expressing the 'Tao of Ruby'. With such a compelling recommendation by the creator of Ruby, the book is an easy purchase and should quickly become a much loved companion with your Ruby development in the coming years. The book's list price is $39.99 and is available directly from the publisher for $35.99 or via other booksellers such as Amazon.com.
A Guide to Branching and Merging Patterns
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
Getting Started with Stratos - an Open Source Cloud Platform
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.
No comments
Watch Thread Reply