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 Ian Roughley on Jun 17, 2008
McObject® has released Perst™ version 3.0, a major upgrade of its open source, object-oriented embedded database system. Persist is dual licensed (commerical and GPL), allowing it to be used freely in non-commercial applications.
Persist is describes itself as:
Being ideal for Java applications requiring a modest footprint and fast, multi-platform data management. Typical uses include packaged software, mobile and embedded applications, Web services and industrial systems. With a run-time code footprint of between 30K and 300K, Perst fits well within the resource constraints of many embedded systems.
Persist also reduces some of the complexities of working with object-oriented databases:
Perst’s fundamental achievement lies in making persistent Java objects as efficient and easy to use as possible. In most cases, Perst automatically loads the persistent objects without explicit programmer command. When used with aspect-oriented tools such as AspectJ and JAssist, Perst provides completely transparent persistence.
Unlike many other object-oriented databases, Perst requires no dedicated compiler, byte code processor or specialized Java run-time environment, yet provides a high degree of application transparency. The Perst API is convenient, flexible and easy to use. Perst requires no end-user administration, and along with its simplicity, Perst ensures integrity via transactions that adhere to the “ACID” properties (Atomicity, Consistency, Isolation and Durability) with very fast recovery.
The new version of the database includes:
Persist can be downloaded from Java.net, the full press release as well Java and .NET version can be downloaded from the McObject's web site.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A Guide to Branching and Merging Patterns
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
I don't like the license terms: The GPL version is only for non-commercial use.
Well, that's not really true now is it. The 2 licenses that are available are commercial and GPL, if it's encumbered by the GPL then it's most definitely not available to be used freely. Note that this isn't an attack on the GPL, which is a fine license, it just irks me when people equate the terms of the GPL with free usage. Oh, and another inaccuracy springs to mind: the GPL explicitly allows commercial usage, albeit under fairly onerous terms, so that part of the intro is wrong as well.allowing it to be used freely in non-commercial applications
Oops! That was meant to be a reply to the original article, not to your comment Thomas.
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.
3 comments
Watch Thread Reply