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 Johan Strandler on Jun 28, 2006
Geronimo applications, server features, and integrated products can be distributed as Geronimo plugins. Plugins are easy to install, automatically download any dependencies, and do not require server restarts. Using the plugin infrastructure, applications or modules can be copied from one Geronimo installation to another (from developer to developer, test to production, etc.). - Deployment plans have been updated, ConfigId has been replaced by a more complete ModuleId structure. Previous releases of Geronimo will require modifications, refer to the Geronimo documentation for further details.
- Tools and commands have been also updated to reflect the ConfigID -> ModuleId change as well as geronimo-config-1.1.xsd -> geronimo-module-1.1.xsd schemas.
- More functionality has been included in the Administrative Console (http://localhost:8080/console/). Memory utilization graphics, more Thread Pools, remote HTTPd configuration wizard and plugins are some of these new features.
- All the applications (except for those deployed via Hot Deployment) are stored in the
/repository directory. Previous config-store has been removed. Enhanced SMTP support. Keystore configuration. Geronimo also supports in-place deployments. This means an archive or a directory can be deployed without being copied into the Geronimo directory structure. Little-G is an alternative distribution offered in Geronimo 1.1. This new distribution has a reduced footprint. It comes with either Tomcat or Jetty as WebContainer options.
Getting Started with Stratos - an Open Source Cloud Platform
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
Monitor your Production Java App - includes JMX! Low Overhead - Free download
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