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 Werner Schuster on Apr 05, 2009
While Clojure's moving towards a 1.0 release, interest in the language has reached other platforms as well.
Clojure-contrib now contains two implementations of Clojure on different platforms. A large part of Clojure's written in Clojure, so the implementatations can share a lot of the code:
Clojure users are experimenting with JVM libraries and frameworks. Clojure focuses on concurrency in one JVM and doesn't have special support for distributed work. Terracotta is a technology that allows to tie JVMs, on the same machine or distributed, together. Paul Stadig has been experimenting with getting Clojure to use Terracotta's features. (A similar project was attempted with JRuby). A recent progress report is promising:
So it looks like three of the biggest issues I had to work around in getting Clojure to work with Terracotta, will be resolved on the Terracotta side. This means that the Terracotta Integration Module that I wrote[3] will pretty much boil down to a configuration file.
Finally, a new Clojure release is available with these changes:
Incorporates all the recent additions - fully lazy seqs, :let option for doseq/for, letfn for mutually recursive local fns, synchronous watches, multi-arg set/union/difference/intersection, counted?, per- defmulti hierarchies, #_ ignore form reader macro, future-calls, future and pcalls/pvalues, defmulti docstrings and metadata, methods/ prefers for multimethod reflection, uniform metadata handling for atoms/refs/agents/vars/namespaces, condp, release-pending-sends, AOT tweaks to support applets and Android, etc. All this in addition to many fixes and enhancements.
The changes include the updated lazy behavior of sequences. The multimethod reflection support allows to look at the mapping between dispatch values and functions (using the methods function).
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
Monitor your Production Java App - includes JMX! Low Overhead - Free download
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