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 Nov 10, 2009
T4 is Visual Studio’s built-in code generator. Though fundamental for many of the frameworks built atop .NET, it is none the less incredibly under-powered. Even the simplest things like intelligently reusing templates or emitting multiple files seem beyond it at first glance. Yet developers are finding of ways to incrementally improve it. One such developer, Damien Guard, has built an extension to solve the multiple-output limitation.
Damien Guard’s Manager class takes over control of rendering the output so that it can be split into multiple files. Implemented as a template file itself, it is both easy to understand and yet quite clever. Out of the box it supports useful things like common headers and footers that are applied to all files in the set.
Damien recently published an improved version of his manager class. The most important change is its improved support for source control. It will now check to see if files have changed before writing them to disk. If a file has changed, it will be automatically checked out. There are also some internal improvements to reduce conflicts with other plugins that may be watching for changing files.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Case Study: IBM's Agile Transformation
Five Key Practices to Agile ALM
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.
No comments
Watch Thread Reply