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 Scott Delap and Craig Wickesser on Aug 22, 2007
Until relatively recently programming languages have fit neatly into either "imperative" or "functional" categories. Scala represents a new breed of language which obliterates these arbitrary restrictions.According to a blog post by David Rupp, Scala just might be The Next Next Java. Comments like this make it worth a look.
There are several key features provided by Scala which demonstrate its object-oriented nature. For example, every value in Scala is an object, this includes basic data types (i.e. booleans, numbers) as well as functions. Additionally, classes can be subclassed and Scala provides a mixin-based composition.
As opposed to languages that only support single inheritance, Scala has a more general notion of class reuse. Scala makes it possible to reuse the new member definitions of a class (i.e. the delta in relationship to the superclass) in the definition of a new class. This is expressed as a mixin-class composition.
Some of the key functional concepts provied in Scala include higher-order functions, currying, nested functions, sequence comprehensions, and more.
Scala is statically typed which allows it to provide generic classes, inner classes and even polymorphic methods. One other thing worth mentioning is that Scala was designed to interoperate with Java and .NET. The current version of Scala does not run on .NET (although the previous version did). There are plans for Scala to run on .NET in the future.
Scala also interoperates with Java. It uses a compiler, scalac to convert source files into Java class files (i.e. bytecode that runs on the JVM). You can access and use all Java classes from Scala, and you can also access Scala code from a Java application. To quote David Rupp,
It also has access to the multitudinous multitudes of existing Java libraries out there, making for a (potentially) easier migration path.This allows Scala to make use of the vast collection of Java libraries and frameworks that have already been written for Java 1.4, 5.0, or 6.0 which Scala is regularly tested on. Scala may also work with older versions of Java but there is not formal testing done for those situations. Scala is distributed under a BSD license and has been deemed stable for several years.
This all leaves the question "Why should I use Scala?". Scala was designed with one goal in mind,
To create a language with better support for component software. (The Scala Programming Language, Donna Malayeri)The idea is that software should be developed such that it can be constructed from re-usable parts. Scala aims at providing a programming language which unifies and generalizes key concepts from both object-oriented and functional styles.
It was through this one goal and design that Scala is able to provide some great features including...
Scala brings Erlang style actor based concurrency on the JVM. Developers can now design scalable concurrent applications on the JVM using the actor model of Scala which will automatically take advantage of the multicore processors, without programming to the complicated thread model of Java.
The style and features provided by Scala have left numerous developers interested in Scala, such as Debasish Ghosh who stated,
I have been playing around with Scala for quite some time and have been thoroughly enjoying the innovations that the language offers.
To summarize, Scala is a functional object-oriented language which provides a seamless blend of features not found elsewhere, all while running on the JVM. With an increasing interest by developers and increasing tool support Scala is certainly becoming a language to have in your tool belt.
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
While the current version of the Scala distribution does not run on .NET, interested Scala users may install the sbaz-package "scala-msil" which contains additional tools and libraries (alpha stage software) to run Scala on Mono/.NET.
The Scala distribution is actually built and tested every night on the Sun Java 1.4, 1.5, 1.6 and IBM Java 1.5 platforms; the latest nightly build is available from the Scala website.
The Scala distribution is released under a BSD-like license unless otherwise specified.
Other features of Scala can be found in the online document "A Tour of the Scala Programming Language". A history of most language changes introduced in Scala 2 (appeared in March 2006) is available from the Scala Change Log page.
I fired up the Scala/Eclipse plugin a couple months ago to try some playing with Lift; the plugin's not bad, but it's a far cry from the Java tooling still. Ultimately, I had too much cognitive load at the time to really make progress on learning the ins and outs of Scala, so I set it aside for a time when I'm not already neck-deep in learning for my day-job.
I agree, the Scala Plugin for Eclipse could use some lovin' :) If it could at least add code-completion/content assist, it would be so much better.
But it is fun learning Scala, I am looking forward to reading more about Scala and hoping the Pragmatic guys write a book for it :)
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.
3 comments
Watch Thread Reply