Standard relational isolation levels, and durability options are built-in. All of these capabilities are brought with Front-Tier up into the application server tier, where they are closely linked to the applications that use it, yet shared to enhance concurrent access and ensure transactional consistency. Often these mechanisms force each application instance to cache its own copy of the data and require adoption of event-driven concurrency mechanisms to prevent accidental data corruption. Front-Tier equips developers with all the controls they need to optimally tune their applications. Much of the product is parameterized so that programmers can invoke the features most appropriate for their application scenario, whether their priority is maintaining the highest performance possible for the largest number of concurrent users, or ensuring the highest level of data and transaction durability.
Applications can specify lock time-out durations.
Transaction logging may be turned on or off. Plus, when on, logging may be set to varied levels of transaction durability. Data stores may be permanent or temporary, durable logged to disk or entirely diskless. Diskless logging may be employed, enabling the transaction semantics of commit and rollback, but without the performance costs of disk logging. Replication of entire Front-Tier caches, or individual tables, can be configured to enable high reliability in 24x7 environments.