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 Sep 14, 2008
DataNucleus, the successor to the Java Persistence Platform JPOX, has released DataNucleus Access Platform 1.0.0 which provides access to a range of datastores for Java applications using JDO/JPA API's.
DataNucleus Access Platform 1.0.0 is fully compliant with JDO1, JDO2, JDO2.1, JPA1, and provides preview features for JDO2.2 and JPA2. It currently supports persistence to RDBMS, db4o, LDAP, XML, Excel, NeoDatis ODB, and JSON. It additionally allows configuration of classes to be persisted using JDO annotations/XML or JPA annotations/XML providing access to both JDO and JPA APIs regardless of which configuration method was chosen. Querying of the supported datastores can be performed using JDOQL, JPQL or SQL (dependent on the datastore). By making use of standardized APIs, the process of swapping persistence from one datastore to another is a simple URL change when specifying the datastore. AccessPlatform is made up of a series of OSGi compliant jars, and can be utilized in J2SE, J2EE, or OSGi container environments. By using OSGi together with eclipse extension-points, DataNucleus is extensible and provides support for your own datastore.
DataNucleus Access Platform provides the next generation of Java Persistent Objects (JPOX), and adds support for:
DataNucleus Access Platform is provided under the Apache 2 open source license.
Documentation is available to view online (or PDF).
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
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
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
18 agile and lean practices for effective software development governance
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