Distributed lock overview

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Locks are used to provide mutually exclusive access to a resource. For example, you can use a lock to:

Provide exclusive access to a database row, table, or an entire database
Lock reading messages from a queue in a sequential manner

Any resource that is shared where updates occur can be the target for a lock. Locks are usually used on operations that mutate state, not on reads.

Each lock has a name. The application determines the resources that the named lock accesses. Typically, multiple instances of the same application use this named lock to exclusively access the resource and perform updates.

How-To: Use a lock

Mon, 01 Jan 0001 00:00:00 +0000

Now that you’ve learned what the Dapr distributed lock API building block provides, learn how it can work in your service. In this guide, an example application acquires a lock using the Redis lock component to demonstrate how to lock resources. For a list of supported lock stores, see this reference page.

In the diagram below, two instances of the same application acquire a lock, where one instance is successful and the other is denied.

Distributed lock on Dapr Docs

Distributed lock overview

Introduction

How-To: Use a lock