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 Jonathan Allen on Oct 25, 2008
When Microsoft, along with HP and Intel, offered the C# Standard to ECMA in 2000, it was a major break in tradition. Up until that point, all programming languages developed by Microsoft were controlled solely in-house. While documentation was certainly provided, the general populace never got the in-depth to really explore the nooks and crannies of the language, let alone write their own compiler.
An unfortunate side effect of being a standard is that it is written like one. Often the standard will say a compiler may do something but is not required to. While this is fine at a conceptual level, it makes it harder than necessary to what the Microsoft C# compiler actually does.
This where the book by Jagger, Perry, and Sestoft comes into play. They take the C# 2.0 standard and fill in the blanks. This book is full of detailed information on how the Microsoft choose to implement its C# compiler. And though possibly dated, it also includes the same information on Mono's C# compiler.
The real value of this book comes from its discussion of edge cases. For example, the standard includes a section on the FGAB problem. Specifically if F(G<A, B>(7)) should be interpreted as F having the arguments G<A, B> and 7 or the arguments (G<A) and (B>7). While not much of an issue in C# 2, this far more important now that passing functions to other functions is becoming common. The authors build on the standard both by clarifying the rather esoteric text and by describing how the compilers actually handle it. (Both Microsoft and Mono simply fail to parse it in this case.)
If any complaints are to be made about this book, it is that it tends to be very dry and technical. While they do include a lot of background information about how the language came to be, it never quite gets to the conversational level we find in Framework Design Guidelines.
Annotated C# Standard by Jon Jagger, Nigel Perry, and Peter Sestoft is currently in print and also available via Google Book Search.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
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