* A single-writer/multiple-reader MVCC based transactional concurrency model. SQL style nested sub-transactions are supported. Clients may concurrently access a single LSM database from within a single process or multiple application processes. * An entire database is stored in a single file on disk. * Data durability in the face of application or power failure. LSM may optionally use a write-ahead log file when writing to the database to ensure committed transactions are not lost if an application or power failure occurs. * An API that allows external data compression and/or encryption routines to be used to create and access compressed and/or encrypted databases.

* 100% compatible drop-in replacement for Lua 5.1, based on LuaJIT 2.1. Simply use #!/usr/bin/tarantool instead of #!/usr/bin/lua in your script. * full support for Lua modules and a rich set of own modules, including cooperative multitasking, non-blocking I/O, access to external databases, etc * MsgPack data format and MsgPack based client-server protocol * two data engines: 100% in-memory with optional persistence and a 2-level disk-based B-tree, to use with large data sets * multiple index types: HASH, TREE, RTREE, BITSET * asynchronous master-master replication * authentication and access control * the database is just a C extension to the app server and can be turned off