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 Abel Avram on Mar 11, 2009
In this presentation recorded during QCon London 2008, Christophe Coenraets presents Flex and AIR, two technologies from Adobe used to create, deploy and run Rich Internet Applications. After a brief introduction to each technology, Coenraets showed some applications built with them.
Watch: Rich Internet Applications with Flex and AIR (1h 5 min.)
AIR stands for Adobe Integrated Runtime, which is simply another runtime used to run Flash, HTML and JavaScript applications on the desktop. AIR is a cross platform runtime for Mac OS X, Windows, and Linux.
Flash applications don’t necessarily need a browser to run, but they can run on AIR directly on the desktop. The idea is to provide a better integration with the desktop, avoiding the limitations introduced by browsers, and ensuring an offline experience when necessary. AIR also offers access to the underlying operating system API and other features:
The development environment for AIR applications is Flex. Flex supports two programming languages: ActionScript, an ECMAScript language fully compliant with version 4, and MXML, which is an XML-based user interface markup language. The code written in one of those two languages is compiled into bytecode executed by Flash’s runtime or AIR.
A large part of the session consists of presentations of a number of applications intended to demonstrate the capabilities of Adobe’s technologies.
Getting Started with Stratos - an Open Source Cloud Platform
A practical guide to choosing the right agile tools
18 agile and lean practices for effective software development governance
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.
2 comments
Watch Thread Reply