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 Abel Avram on May 22, 2009
Microsoft has included F# in VS 2010 Beta 1 and has released a corresponding CTP update for VS 2008. The latest binaries, version 1.9.6.16, are not compatible with previous ones, v. 1.9.6.2, meaning all previous code needs to be recompiled.
Microsoft has not only included F# in Visual Studio as promised in 2007 by adding it to VS 2010 Beta 1 with support for .NET 4.0, but it has also created a VS 2008 CTP update for those who don’t want to use a beta but a more stable IDE along with .NET 2.0-3.5.
Don Syme’s detailed release notes mention a binary incompatibility:
F# binaries compiled with this new release are incompatible with binaries from previous releases, so must be recompiled. Binary compatibility for F# is an aim of the RTM release of Visual Studio 2010.
Another significant breaking change is using the lightweight syntax (#light) by default. That makes the code whitespace-significant by default. The MSDN Walkthrough contains examples that do contain illegal whitespaces which need to be removed.
Useful links: Release Notes, InfoQ interview: Don Syme Answering Questions on F#, C#, Haskell and Scala, F# Content on InfoQ, PDC Presentation on F# by Luca Bolognese (beginners), MSDN Walkthrough of F# in Visual Studio 2010, MSDN Visual F# Documentation, MSDN F# Code Gallery.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A practical guide to choosing the right agile tools
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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