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 Jan 09, 2008
Yesterday we told you about using PHP.NET with Silverlight. The GUI framework for Silverlight, WPF, represents the future of Windows development. So it is understandable that F# developers would be looking at it with a keen eye as well.
John Liao has been working through Petzold's book, Applications = Code + Markup, from a F# viewpoint. He explains his reasons for doing so,
Why did I pick F# as the target programming language to translate the code to? Well, which the advent of multicore processors, functional programming languages seems naturally suited to the new hardware architectures. In addition, Wall Street Journal made a passing reference to F# in the article Behind Microsoft's Bid to Gain Cutting Edige. I figure if Wall Street Journal have an article about F#, it seems about time that F# will become mainstream. Having two F# books coming out also helps developers to start learning about this language by Microsoft.
In the process he is uncovering some design choices in the F# language that make working with WPF harder than it should be. For example, F# does not generate static read-only fields. Lewis Bruck mentions this as a problem for F#/SQL Server integration as well.
A list of John Liao's posts has been compiled by Don Syme.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
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