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 on Mar 09, 2009
The Flight Framework is a recent addition to the ever-growing set of MVC frameworks for application development in Adobe Flex. Tyler Wright, Rob Taylor, and Jacob Wright created the Flight Framework to meet their ActionScript and Flex development needs, and recently open sourced it in beta under the MIT license. Tyler discusses the release on his blog:
The Flight Framework is the evolution of an ActionScript framework that has been around for a few years. It was a replacement to Cairngorm and was originally designed for web-based, design-centric applications such as logo makers and book builders. Even now the framework ships with the CommandHistory - an entire solution for undo and redo - and other practical utilities that strengthen its offering.
Flight Framework maintains an emphasis on supporting capable clients: Flex and Flash applications that are much more than just a pretty face to a server implementation. Through features like domains (modular MVC systems) and a prescribed structure, the framework transforms component scripting into real application development.
In describing the framework, the creators often liken it to Cairngorm, but without all of the “boiler-plate” code. The project blog describes the framework in more detail:
The framework prescribes a Model-View-Controller workflow that minimizes the complexity of application development. It modularizes domain logic, streamlines team development, and creates a natural iterative programming environment. Most importantly, Flight Framework is designed to make your day to day coding experience as simple and enjoyable as possible.
Flight is a minimalist. Everything from its size to its prescribed processes ensure that you never have to do more than is absolutely needed.
...
The Flight Framework prescribes a common structure and methodology that can be leveraged throughout all tiers of your application.
...
A Flight application is made up of a series of one or more MVC modules, or domains. Each domain under Flight represents a specific business domain, or a real-world set of related problems and solutions. Domain examples are infinite and range anywhere from a user account to an entire shopping cart, from an application’s screen flow to a full image-editing library. These MVC subsystems are defined by you, reflecting your application goals, and are unique to their specific purposes. Some domains are completely self-contained and are reused across many projects, while others have dependencies among each other or the application. Domains can even be organized hierarchically, a high-level domain wrapping a group of sub-domains, for greater modularization and manageability of a complex system. Though a powerful tool, domains are simple enough and easy to approach in development. In Flight, well-defined domains will be the strength of your application development.
Learn more about the Flight Framework on the project site: http://www.flightxd.com.
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