Redis will supports for transactions and can group multiple Redis commands together to insure that they get executed as single unit, which will not be interrupted and all the the commands will be executed. Another way to say this that Redis transactions are atomic. In Redis transactions are started using the multi command. Any commands entered after this point are cued by Redis until either the exact or Discard commands. There is one really important thing to understand about Redis transactions. And are actually queuing up the commands for the transactions, when the user run the transaction it will actually fail and it won't run any of the commands. The only time that res will actually run commands after an error has occurred is if that error occurs when the transaction is actually executing as opposed to when the commands are being queued up to be executed.

The transaction commands explain the basic functionality of Redis database

The following example describes the basic functionality of a transaction in Redis database. [c] redis 127.0.0.1:6379> MULTI OK redis 127.0.0.1:6379> SET preparing redis QUEUED redis 127.0.0.1:6379> GET preparing QUEUED redis 127.0.0.1:6379> INCR visitors QUEUED redis 127.0.0.1:6379> EXEC OK "redis" (integer) 1 [/c]

• Transaction - Supports for multiple groups in Redis commands for insuring the interrupted and executed key values.
• Transaction commands - Describe the basic functionalities of Redis database.