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 Ryan Slobojan on Aug 29, 2007
Apache Geronimo, an open-source Java Enterprise Edition (Java EE) application server, recently released version 2.0.1. InfoQ took the opportunity to learn more about Apache Geronimo and where it fits into the application server space.
Apache Geronimo 2.0.1 is the first Java EE 5 compatible version of Geronimo, and the eighth Java application server to be certified as Java EE 5 compliant. Despite the version number, version 2.0.1 is the first release of the 2.x code branch - the 2.0 release was cancelled when a critical security problem was discovered. This version of Geronimo brings several major changes from the previous release:
Matt Hogstrom, chairman of the Apache Geronimo Project Management Committee, recently discussed the apparent low adoption rate of Geronimo, saying:
I think one of the issues we faced as a project is that we came to the J2EE game too late. You already had WebSphere and WebLogic dominating the commercial space and really JBoss was the only real dominant open source player. Geronimo came in to an already saturated market so getting people to run over to simply change was difficult.
Today we're certified Java EE 5.0 before some commercial application servers as well as other open source servers. At this point I think we're in on the beginning rather than coming late to the game. Its not going to be easy as people are comfortable with their app server choices from before but Geronimo is coming to the table early and has a good opportunity.
There are also questions about the future plans for Geronimo, including whether Geronimo will adopt the OSGi standard. Hogstrom said that migrating from Geronimo's GBeans architecture poses some difficulties due to structural differences between it and OSGi, but that it was being discussed now that JSR 291 (the OSGi JSR) has been finalized.
Getting Started with Stratos - an Open Source Cloud Platform
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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.
1 comment
Watch Thread Reply