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 Rob Thornton on Jan 16, 2007
Fortress, a new language designed specifically for high-performance computing (HPC), has been released on SunSource under the BSD language. The preliminary interpreter is based on the JVM. Fortress is intended as a modern day replacement for Fortran.
Fortress was created as part of Sun's work on the DARPA HPCS program. Sun has since been knocked out of the program, but Guy Steele has continued work on the language. X10 from IBM and Chapel from Cray are also HPC languages under development.
While the Fortress interpreter is currently based on the JVM, it is a new language and has not been tied to any legacy language syntax or semantics. To tailor itself to the HPC programming, Fortress supports mathematical notation and static checking of physical units and dimensions. Also, many of the core language constructs are parallel by default, helping to tailor it to multi-core systems. There are signs that Fortress may not stay on the JVM, but may eventually have its own virtual machine. For instance, Fortress has a different memory model than Java and, according to the latest language specification (still in alpha), it will support some form of software transactional memory (STM).
Fortress is currently only an interpreted language, but the intention is to make an optimizing compiler available at some point in the future.
Getting Started with Stratos - an Open Source Cloud Platform
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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