跳到主要内容

Distributed Lock API demo with redis

This example shows how to call redis through Layotto to trylock/unlock.

The architecture of this example is shown in the figure below, and the started processes are: redis, Layotto, a client program with two goroutines trying the same lock concurrently.

img.png

step 1. Deploy Redis and Layotto​

with Docker Compose​

You can start Redis and Layotto with docker-compose

cd docker/layotto-redis
# Start redis and layotto with docker-compose
docker-compose up -d

Compile locally (not for Windows)​

You can run Redis with Docker, then compile and run Layotto locally.

[!TIP|label: Not for Windows users] Layotto fails to compile under Windows. Windows users are recommended to deploy using docker-compose

step 1.1. Run Redis with Docker​

  1. Get the latest version of Redis docker image

Here we pull the latest version of the official image:

docker pull redis:latest
  1. View the local mirror

Use the following command to check if redis is installed:

docker images

img.png

  1. Run the container

After the installation is complete, we can use the following command to run the redis container:

docker run -itd --name redis-test -p 6380:6379 redis

Parameter Description:

-p 6380:6379: Map port 6379 of the container to port 6380 of the host. The outside can directly access the Redis service through the host ip:6380.

step 1.2. Compile and run Layotto​

After downloading the project code to the local, enter the code directory and compile:

cd ${project_path}/cmd/layotto
go build

The layotto file will be generated in the directory, run it:

./layotto start -c ../../configs/config_redis.json

step 2. Run the client demo​

The client demo invokes Layotto API to lock and unlock the resource.

Go​

 cd ${project_path}/demo/lock/common/
 go build -o client
 ./client -s "lock_demo"

If the following information is printed, the call is successful:

client1 prepare to tryLock...
client1 got lock!ResourceId is resource_a
client2 prepare to tryLock...
client2 failed to get lock.ResourceId is resource_a
client1 prepare to unlock...
client1 succeeded in unlocking
client2 prepare to tryLock...
client2 got lock.ResourceId is resource_a
client2 succeeded in unlocking
Demo success!

Java​

Download java sdk and examples:

git clone https://github.com/layotto/java-sdk

Change directory:

cd java-sdk

Build:

# build example jar
mvn -f examples-lock/pom.xml clean package

Run the examples:

java -jar examples-lock/target/examples-lock-jar-with-dependencies.jar

And you will see:

TryLockResponse{success=true}
TryLockResponse{success=true}
TryLockResponse{success=true}
UnlockResponse{status=SUCCESS}
TryLockResponse{success=true}
UnlockResponse{status=LOCK_UNEXIST}

Next Step​

What did this client Demo do?​

The demo client program uses the golang version SDK provided by Layotto, calls the Layotto distributed lock API, and starts multiple goroutines to do locking and unlocking operations.

The sdk is located in the sdk directory, and users can call the API provided by Layotto through the sdk.

In addition to using sdk, you can also interact with Layotto directly through grpc in any language you like.

In fact, sdk is only a very thin package for grpc, using sdk is about equal to directly using grpc.

Details later, let's continue to experience other APIs​

Explore other Quickstarts through the navigation bar on the left.

Understand the design principle of Distributed Lock API​

If you are interested in the design principle, or want to extend some functions, you can read Distributed Lock API design document