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 Jon Rose and Scott Delap on Aug 06, 2007
Adobe continues to court the Open Source developer community with significant parts of the runtime coming from Open Source projects. The Web2.0 Journal relays Adobe's breakdown of the major Open Source runtime components below:
Adobe described the open source AIR as including a WebKit HTML engine, an ActionScript Virtual Machine (the Tamarin Project) and an SQLite local database with full text search same as Google Gears is using - and the two should have a common API soon enough.An overview of the components:
Adobe's provided a handful of reasons in their FAQ for choosing WebKit over other options like the Gecko engine.
- Open project that we could contribute to
- Proven technology, that web developers and end users are familiar with
- Minimum effect on Adobe AIR runtime size
- Proven ability to run on mobile devices
The Tamarin is a joint effort between Adobe and the Mozilla Foundation to build an Open Source implemenation of the ECMAScript 4th edition (ES4) language specification.
The project home page articulates their main goal:
Adobe and Mozilla hope to accelerate the adoption of a standard language for creating engaging Web applications.
SQLite is a small C library that implements a self-contained, embeddable, zero-configuration SQL database engine.
Adobe AIR has created a lot of buzz in the industry. Here is some of what is being said...
Jesse James Garrett, who coined the term "Ajax", had favorable comments in a Wired article about AIR:
...I think that Ajax developers have kind of been running up against the constraint of the browser for a while now," says Garrett. "There's a lot of code from your browser application that you'd have to throw out for the offline portion of your app ... The advantage of AIR is the re-usability of that code outside the browser...
Others, such as Jesse Warden, are not so positive however:
...I am not interested in developing for AIR, Adobe Integrated Runtime. While the features sound compelling, they do not offer me anything I need in my day to day development for clients. I do not believe the market, currently, has a supporting model for those types of applications in a compelling way. AIR additionally does not offer anything new beyond it being a Flash projector wrapper with Adobe's name behind it...Adobe's Ryan Steward counters Warden's position however, saying:
Adobe AIR is clearly a technology that a lot of people see differently. I think most of that is due to the fact that this is a very new type of technology... The great thing about AIR in my mind is that it gives developers a very "webby/browser" experience on the desktop. That includes the obvious benefit of being able to write in web technlogies (Flash, Flex, JavaScript, HTML) but it's more than that. AIR applications have a quick, easy install experience that is closer to the browser's zero install. It runs cross platform just like the web browser.Ryan does acknowledge that AIR is still in the early stages and will have to evolve.
...No, you can't use plugins or access native code/applications. That sucks and it's a problem for some developers. But AIR is a 1.0 product and the cross platform aspect is important to us. No, AIR doesn't do windowed hardware acceleration (it does it for video in full screen mode), but again, it's a 1.0 product and we don't have time to put everything in.InfoQ will continue to monitor the traction gained by Adobe AIR and similar technologies, like Google Gears, in the months to come.
Monitor your Production Java App - includes JMX! Low Overhead - Free download
18 agile and lean practices for effective software development governance
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
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