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 Mirko Stocker on Mar 29, 2010
Rhomobile, the company behind the Rhodes framework that allows developers to write native applications for almost all smartphone platforms in Ruby, has just released version 1.5. Rhodes applications are written once and then compiled to run on almost all smartphone platforms. Currently supported are the iPhone, BlackBerry, Windows Mobile, Symbian and Android; there are also plans to support Intel and Nokia's MeeGo and Palm's Web OS in the future.
But with HTML 5 on the horizon, why should people want to write native applications? We asked this question Adam Blum, Rhomobile's CEO:
We like HTML5 and you can use HTML5 in the views of your Rhodes-based native smartphone app. But there will always be a need for local installable native apps that take advantage of native device capabilities, the vast majority of which will never appear as an HTML tag. Also, support of the framework for automatically synchronized local data in the Rhodes framework makes it far easier to build apps that provides offline, disconnected data to users than is possible with just HTML5 SQL support alone. The success of the iPhone app store on a device with a good browser demonstrates that users want and now demand local native apps for their smartphones
A new entry on the company's blog describes what distinguishes Rhodes from other frameworks like PhoneGap:
Rhodes applications are written in HTML and Javascript for the GUI, and Ruby. With Ruby, it's even possible to use RubyGems (Gems with native extensions obviously don't just work, but Rhodes supports native Gems like net/http(s), JSON, REXML, crypt, openssl).
Being native applications, you can also access the GPS, PIM contacts, the camera, and other devices that are not accessible from a pure web application.
The latest release Rhodes 1.5 added some improvements like "native geo mapping for android", "native screen resolution for iPad" and support for splash screens.
Rhodes can be used either free of charge under a GPL license or by buying a per-application-license for $500. A list of applications built with Rhodes can be found, for example, Wikipedia's iPhone app is developed with Rhodes, in "approximately 20% of the code of their previous mobile app written in Objective C for the iPhone".
Mobile and the New Two-Tiered Web Architecture
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
A practical guide to choosing the right agile tools
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Getting Started with Stratos - an Open Source Cloud Platform
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