Free transactional storage software for mac

S3 browser is a Mac OS X administration tool for the Amazon S3 storage service. My goal is to build a small application useful in itself for developers or users subscribed to the S3 service, but also to provide example code showing how to access S3 through the REST API in a OS X Objective-C client application, on top of OS X technologies (Keychain, URL loading system, ...).

Basic S3 operations are implemented (bucket list/create/delete), objects deletion, upload and download (using streaming network code to be able to deal with large files). S3 Browser also has a small low-level request inspector and a task console.

Oracle Berkeley DB Java Edition is a high performance, transactional storage engine written entirely in Java. Like the highly successful Berkeley DB product, Berkeley DB Java Edition executes in the address space of the application, without the overhead of client/server communication.
It stores data in the applications native format, so no runtime data translation is required. Berkeley DB Java Edition supports full ACID transactions and recovery. It provides an easy-to-use, programmatic interface, allowing developers to store and retrieve information quickly, simply and reliably.

Main features:
- Local, in-process data storage.
- Schema-neutral, application native data storage.
- Keyed and sequential data retrieval.
- Easy-to-use Java Collections API.
- Persistence API for accessing Java objects.
- Single process, multi-threading model.
- Record level locking for high concurrency.
- Support for secondary indexes.
- In-memory, on disk or both.
- Configurable background cleaner threads re-organize data and optimize disk use.
- Full ACID compliance.
- Selectable isolation levels and durability guarantees, configurable on a per-transaction basis.
- Managed transactions using the Java Transaction API (JTA).
- J2EE application server integration using J2EE Connector Architecture(JCA).
- Provides support for monitoring, auditing and administration using the Java Management Extensions (JMX).
- Catastrophic and routine failure recovery modes.
- Timeout based deadlock detection.
- Hot and cold backups, log file compaction, and full database dumps.
- 100% pure Java for portability and ease of development.
- Single JAR file - easy to install, runs in the same JVM as the application.
- Java 1.4.2 or later Standard Edition JVM required.
- Programmatic administration and management-zero human administration.
- API for routine administrative functions.
- Small footprint 772KB.
- Scalable to terabytes of data, millions of records.
- Source code, test suite included.

System requirements:
-

Enhancements
- Fix a bug that somtimes causes two log cleaner threads (when multiple threads are configured or multiple app threads call Environment.cleanLog) to select the same file to clean. This can result in two attempts to delete the log file after cleaning. The second attempt causes an exception to be traced repeatedly, but no other side effect. The problem is transient and goes away if the Environment is closed and re-opened. An example of the exception is below. The symptom is that this exception occurs repeatedly, and the file is not present.
- Fix a bug that could cause a LogFileNotFoundException when using an XAEnvironment, if a prepared transaction is not ended prior to a crash and then the prepared transaction is aborted after recovering from a crash. [#17022] (3.3.79)
- Fix a bug that prevented deferred-write record deletions from being made durable by Database.sync, if a crash occurs after Database.sync but prior to the next checkpoint. Under rare circumstances this could also result in a LogFileNotFoundException later when accessing the deleted entry. [#16864] (3.3.78)
- Fix a bug that prevents log cleaning from functioning properly when a temporary DB (DatabaseConfig.setTemporary) is large enough to overflow the JE cache. Also fix a bug that could in rare cirumstances cause an endless loop while performing log cleaning. [#16928] (3.3.78)
- Fix a bug that caused an infinite loop under certain timing dependent circumstances when using EnvironmentConfig.setSharedCache(true). This bug was reported in two different forum posts. Thanks to Kevin Jackson and Vyacheslav Lukianov for reporting it! [#16882] (3.3.78)
- Improve output of partial information in DatabaseEntry.toString. Thanks to archie172 for reporting this on OTN. [#16929] (3.3.78)
- Fix a bug in SecondaryCursor.dup that required the cursor to be initialized. This method, like Cursor.dup, may now be called whether the cursor is initialized or not. Thanks to archie172 for reporting this on OTN. [#16930] (3.3.78)
- Fix a bug that caused NullPointerException when opening an XAEnvironment under certain circumstances, when prepared but uncommitted transactions are present in the JE log and must be replayed during recovery. This bug was reported on the OTN forum by Matthieu Bentot -- thank you Matthieu! An example of the stack trace is below.
- Fix a bug that caused LogFileNotFoundException in rare circumstances for an Environment having one or more Databases configured for duplicates (or one or more SecondaryIndexes with MANY_TO_XXX relationships). The bug only occurs when a single secondary/duplicate key value is associated with a large number of records/entities; specifically, the sub-Btree for a single duplicate key value must have at least 3 levels. [#16712] (3.3.76)
- Fix a bug that caused BufferOverflowException while writing transactional records. This could occur if multiple threads were writing to an environment while using the same Transaction. [#17204]
- Direct Persistence Layer (DPL), Collections and Bind packages - Fix a bug that causes the EvolveStats returned by EntityStore.evolve to contain zeros, even when entities are evolved and written, when no EvolveListener is configured. Thanks to jhalex on OTN for reporting this. [#17024] (3.3.78)

monotone works out of a transactional version database stored in a regular file.
Monotone is a free distributed version control system.
It provides a simple, single-file transactional version store, with fully disconnected operation and an efficient peer-to-peer synchronization protocol.
It understands history-sensitive merging, lightweight branches, integrated code review and 3rd party testing.
It uses cryptographic version naming and client-side RSA certificates.
It has good internationalization support, has no external dependencies, runs on linux, solaris, OSX, windows, and other unixes, and is licensed under the GNU GPL.
Enhancements:
- Private keys are now stored per-user, rather than per-db, and in a more standard format. Several command line enhancements, for instance add --unknown, drop --missing, and revert --missing.
- A new "h:" selector to easily refer to branch heads.
- Enhancements to server permissions support to make granting/revoking access easy without restarting the server.
- More user-friendly handling of database lock contention.
- Fixes to multibyte character handling.
- Improved delta storage handling (gives 0-50% improvement in database size).
- Many small bugs were fixed and enhancements added.

Tivoli Storage Manager 3.7.2 is designed to meet all your needs of information management by delivering a true end-to-end solution spanning the entire enterprise.

Tivoli Storage Manager is an enterprise-wide solution integrating automated network backup, restore and archive, storage management and disaster recovery functions utilized by more than one million systems worldwide. Tivoli Storage Manager is the successor to the IBM and Tivoli ADSM storage management software product set.

Requirements:
Mac OS X 10.2 or later.

Sophic is a Denver-based design firm that specializes in creating identities for small businesses worldwide who need custom, professional design work that’s affordable.

Sophic operates on our relationship-based transactional model.

This strategy fosters high volume, low-overhead style projects with fast turnarounds and lots of word-of-mouth advertising referrals that have a high signing rate.

Neo4j 1.0 Beta 7 is yet another great addition to your computer. It is actually a free and open source graph database. It acts as an embedded, disk-based, fully transactional Java persistence engine that stores data structured in graphs rather than in tables.

A graph (mathematical lingo for a network) is a flexible data structure that allows a more agile and rapid style of development. You can think of Neo4j as a high-performance graph engine with all the features of a mature and robust database. The programmer works with an object-oriented, flexible network structure rather than with strict and static tables yet enjoys all the benefits of a fully transactional, enterprise-strength database.

In addition, Neo4j includes the usual database features: ACID transactions, concurrency control, transaction recovery, durable persistence, and everything else you would expect from an enterprise-strength database.

Major Features:

1. An intuitive graph-oriented model for data representation. Instead of static and rigid tables, rows and columns, you work with a flexible graph network consisting of nodes, relationships and properties.
2. Adisk-based, native storage manager completely optimized for storing graph structures for maximum performance and scalability.
3. Massive scalability. Neo4j can handle graphs of several billion nodes/relationships/properties on a single machine and can be shared to scale out across multiple machines.
4. A powerful traversal framework for high-speed traversals in the node space.
5. A small footprint. Neo4j is a single

Enhancements:

• API: Removed a number of deprecated methods (primarily for relationship type management) from EmbeddedNeas per warning in the previous release.
• API: Transaction is now an interface.
• API: TraversalPosition now has an isStartNode() method.
• API: NotFound and NotInTransaction runtime exceptions have been moved from internal impl package the api package.
• API: getRelationshipById is now exposed in NeoService.
• API: A common base interface for Node and Relationship has been added that contains the set/get/remove property operations.
• Core: Made it easy embed Neo4j in a Spring application. Spring can be configured to use Neo4js transaction manager.
• Core: All known bugs have been fixed.
• Core: Removed singletons and made everything IoC.
• Core: Lots of minor optimization and improvements above native store layer (nioneo).
• Core: Cleanup of code (removed non used code) and improved exception handling.
• Core: Improved read performance and parallelism by implementing MVCC-like features. Nlocks are now taken during read-only operations, instead concurrent operations are working against snapshot versions.