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 Craig Wickesser on Oct 17, 2007
The Eclipse Foundation released the Eclipse Rich Ajax Platform (RAP) 1.0 on Monday. The Eclipse RAP is an Ajax toolkit for creating and deploying Rich Internet Applications geared towards enterprise developers.
InfoQ had a chance to talk with Jochen Krause, RAP project leader, about this first release. Krause was first asked about how Eclipse RAP compared to other Ajax frameworks and platforms:
RAP is based on Equinox, the OSGi reference implementation. It allows developers to structure applications in components (plug-ins), a feature that has been key for Eclipses success. It also allows developers to use Java as their implementation language and comes with an advanced tooling suite, the well established Eclipses JDT and PDE (Plug-in development environment). Finally, RAP allows single sourcing of desktop clients (with Eclipse RCP) and RIA clients (with RAP).
Ian Skerrett sums up the overall use of RAP:
The neat thing about RAP is that you write Ajax applications in Java and use the Eclipse component model based on OSGi. Think of it something like GWT but using Eclipse plugins. This means you can now architect your Ajax applications as extensible components. For large companies this is a big deal since they typically like to create architectures that help them re-use code in different applications.
As reported on Ajaxian.com:
RAP is very different to something like GWT. RAP runs the logic on the server, and emits JavaScript for the controls at runtime (as opposed to compile-time). An implementation of SWT runs on the server and people can extend your views and perspectives to add functionality.
Although RAP provides the ability to use Java, when asked about support for PHP, Ruby or .NET Krause stated that future support for Ruby, and possibly other languages on the JVM, is feasible. Additionally, the RAP website mentions that RAP provides a subset of the SWT API. When InfoQ asked Krause about the status of RAP's conformance with the full SWT API the response was simple:
very broad coverageSpecifically the following items are currently missing,
One hot topic in the Ajax application arena is offline support, such as Google Gears. The Eclipse RAP does not provide offline support but instead, as Krause suggested, Eclipse RCP would be the suitable option.
Finally, InfoQ asked Krause to elaborate on the benefits provided to RAP by its support of Equinox:
- Componentization of applications
- Equinox is a platform that can be executed on very many platforms: devices, desktops, servers.
- Equinox integrates with standard JEE servers (apps can simply be deployed as .war), but apps can also be run standalone.
Some additional information, including screen casts demonstrating the setup and use of Eclipse RAP, can be found at the following links:
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
Monitor your Production Java App - includes JMX! Low Overhead - Free download
18 agile and lean practices for effective software development governance
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