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 Nov 15, 2006
A recent editorial on Ajaxian asks what it would be like to write JavaScript on the client and server. Phobos, a Java.net project, is doing just that. The goal of Phobos, a lightweight web application environment, is to show that Java can be a successful platform for server-side scripting. Server-side JavaScript would allow code-sharing between the client and server and only one language required for web development.
Several recent toolkits (GWT, Ruby on Rails helpers) have focused on allowing developers to write in one language and generate JavaScript code. Instead of this trend, Dion asks:
...maybe we will end up developing end to end in JavaScript? Wouldn't it be nice to be in one language (that is very flexible, and allows you to code functionally, procedurally, OO-ally, etc)?
Michael Mahemoff agrees that server-side JavaScript has a lot of potential, though it was written off after failing in the 1990s in products such as Netscape Enterprise Server. JavaScript has come a long way in the last decade and is now prevalent in most organizations, though usually not the language of choice. Phobos, announced in May, is a web application environment running on the Java platform that is composed of a set of JSR-223 compliant scripting engines, AJAX and Java libraries (Dojo, JDom, etc), and some scripting libraries. Currently they're focused on JavaScript, using Mozilla Rhino as the engine, with some modifications such as the ability to subclass Java classes and support for the JavaScript language extensions for XML.
A Manageaility post asks if we know how we want to develop web applications:
It's quite a paradox, Javascript doesn't have the consistency, modularity and static checking that Java has so someone builds a compiler. Java's type checking system is not quick and dirty enough so someone builds a framework based on Javascript. Can't we ever make up our minds our are we doomed to repeatedly re-invent the way we do things?
Mobile and the New Two-Tiered Web Architecture
Monitor your Production Java App - includes JMX! Low Overhead - Free download
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