Transactions without Transactions
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Dionysios G. Synodinos on May 01, 2008
The open source Java persistence platform JPOX has become DataNucleus for its future direction, due to the significant changes in scope of the project since its initiation.
JPOX is a free and fully compliant implementation of the JDO1, JDO2, JDO2.1 and JPA1 specifications, providing transparent persistence of Java objects. JPOX passed JPA1 TCK in February 2008 making it a JPA compliant persistence framework. It supports persistence to most of the major RDBMS on the market today, persistence to the db4o object datastore, allows querying using either JDOQL, SQL, or JPQL, and comes with its own byte-code enhancer. It also complies with the OGC Simple Feature Specification for persistence of geospatial Java types. JPOX is available under the Open Source Apache 2 license.
DataNucleus extends the scope of JPOX to the application data management domain intent on supporting a wide range of datastores, APIs, services, as well as eventually providing data analysis tools. It is a standards-compliant Open Source Java persistence product which is fully compliant with the JDO1, JDO2, JDO2.1 and JPA1 Java standards. It also utilizes an OSGi-based plugin mechanism meaning that it is extensible.
DataNucleus Access Platform 1.0 ("Faraday") Milestone 1 takes the JPOX codebase and extends it with the following:
Moreover it allows a user to define their persistence using JDO XML/annotations or JPA XML/annotations and then utilize either the JDO or JPA API for persistence (no matter which persistence definition was used), and allow persistence to the full range of datastores.
On the DataNucleus site there are guides demonstrating integration with Eclipse, NetBeans, Maven and Ant.
DataNucleus products will be provided under the Apache 2 open source license.
You can find more information on ORM here: infoq.com/orm
Dionysios G. Synodinos is a Web Engineer and a freelance consultant, focusing on Web technologies
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
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
No comments
Watch Thread Reply