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 Aug 25, 2008
The first alpha release of Boo Lang Studio is available on CodePlex. This Visual Studio add-on strives to offer first class IDE support for Boo, a relatively new .NET language that while inspired by Python, is statically typed.
Since trying to offer a meaningful description of any language in a couple of lines is impossible, we instead offer a link to the Boo Manifesto. Of particular interest is the way it handles late binding, more commonly known today as "duck typing". Unlike most languages that either always or never use late binding, Boo allows developers to declare specific variables as late bound. Another feature rarely found in production languages is an extensible compiler pipeline.
An extensible syntax is only part of what I wanted. The compiler, the compilation process itself should be extensible. Programmers should be able to introduce new actions where appropriate to execute and automate a variety of tasks such as producing documentation and reports, checking coding conventions, applying program transformations to better support debugging or specific execution environments just to cite a few. Programmers should also be able to reuse and/or replace specific compiler components such as the source code parser.
The first alpha release of Boo Lang Studio includes the following enhancements over the earlier prototypes:
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Getting Started with Stratos - an Open Source Cloud Platform
For a great example of developers using Boo in the real world, see the Binsor project, a DSL written in Boo to facilitate configuration of the Windsor dependency injection IOC container.
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.
1 comment
Watch Thread Reply