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 Srini Penchikala on Oct 22, 2008
The latest version of Terracotta, an open source Java clustering framework, supports GlassFish application server, Spring framework and new features like Automated High Availability Mode, Improved Distributed Garbage Collector (DGC) Performance and Visibility, and Cluster-Wide Runtime Statistics. Terracotta development team announced last week the availability of Terracotta 2.7 version.
The new release, which is a follow-on release to Terracotta 2.6, adds support for Spring (versions 2.0.8 and 2.5.4) and Glassfish server (version 2.1). Other new features in version 2.7 include:
Automated High Availability Mode: This feature enables Terracotta server run in an automated restart mode that can be used to automatically back up the cluster data for forensic purposes. This ensures the safety and integrity of clustered data and makes the failover and restart operations easier. Terracotta server cluster can be configured to run in ACTIVE-PASSIVE mode. In this mode, one server runs in ACTIVE mode servicing requests from the clients and one or more servers run in PASSIVE mode acting as a hot standby for the ACTIVE server in case of a failure.
Improved Distributed Garbage Collector (DGC) Performance and Visibility: The distributed garbage collector has been updated to use a generational collection algorithm which provides improvements in GC performance. Generational collectors, which were first introduced in Java 1.4, provide improvements in application performance with little to no overhead. The distributed generational garbage collector in Terracotta server also helps with the throughput in Java applications.
Cluster-Wide Runtime Statistics: Terracotta users can now view and monitor all cluster-related statistics in a single page that provides information on runtime statistics including CPU, heap utilization and transaction rates as well as cache miss, object flush and object fault rates. The cluster visibility features were first introduced in Terracotta 2.6 version.
Certified Patch Process: The new release accepts certified hot patches for systems running in production environment, enabling customers to install them without having to shut down their applications. This avoids any downtime that can occur during a full upgrade maintenance cycle.
Online (Hot) Backup Support: Terracotta introduces a new feature called hot backup feature which helps Web Administrators and Operators to ensure that all Terracotta data files are safely backed up for later restoration. Hot backup features can be used from Terracotta Administrator Console.
Terracotta Integration Module (TIM) Update Center is another new feature that helps the administrators with tasks like managing dependencies of the integration modules, matching release versions, and setting correct configuration and installation options.
In the new release, tc.properties file which is used for controlling throughput tuning settings can be configured with other existing Terracotta settings in the tc-config.xml. Terracotta also has Eclipse integration with the plugin. Release 2.7 is available for download on Terracotta community website after joining the developer community by registering on their website.
More InfoQ coverage on Terracotta clustering framework can be found here.
Srini Penchikala currently works as Security Architect and has 17 yrs of experience in software product management.
Getting Started with Stratos - an Open Source Cloud Platform
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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.
No comments
Watch Thread Reply