https://github.com/unitvectory-labs/lockservicecentral

API that provides a simple interface for distributed locking with lease-based locks, supporting multiple backend systems.
https://github.com/unitvectory-labs/lockservicecentral

Last synced: 5 months ago
JSON representation

API that provides a simple interface for distributed locking with lease-based locks, supporting multiple backend systems.

• Host: GitHub
• URL: https://github.com/unitvectory-labs/lockservicecentral
• Owner: UnitVectorY-Labs
• License: apache-2.0
• Created: 2024-09-16T22:08:59.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-09-18T03:13:46.000Z (over 1 year ago)
• Last Synced: 2024-09-18T06:52:00.054Z (over 1 year ago)
• Language: Java
• Size: 38.1 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0) [![Work In Progress](https://img.shields.io/badge/Status-Work%20In%20Progress-yellow)](https://guide.unitvectorylabs.com/bestpractices/status/#work-in-progress) [![codecov](https://codecov.io/gh/UnitVectorY-Labs/LockServiceCentral/graph/badge.svg?token=43dxfrEyrp)](https://codecov.io/gh/UnitVectorY-Labs/LockServiceCentral)

# LockServiceCentral

API that provides a simple interface for distributed locking with lease-based locks, supporting multiple backend systems. By leveraging a modular architecture, it ensures flexibility and scalability to meet diverse application needs.

## Overview

In distributed systems, managing concurrent access to shared resources is critical to maintaining data integrity and ensuring seamless operations. **LockServiceCentral** addresses this challenge by providing a REST-based API for acquiring, renewing, and releasing named locks for specific clients. The service employs JWT-based authentication to secure lock operations, though authentication can be disabled if required backend microservices are trusted and secured through other means.

**LockServiceCentral** defers the complex part of distributed locking to backend implementations. This modular approach allows a variety of backend systems to handle the intricate details of locking mechanisms.

## Features

- **Distributed Locking:** Manage access to shared resources across multiple instances and services.

- **Modular Backend Support:** Select the appropriate backend for your specific deployment.

- **JWT Protection:** Secure lock operations with JSON Web Tokens, ensuring locks are only accessible to authorized clients.

- **RESTful Interface:** Standardized API endpoints for lock management.

- **Lease-Based Locking:** Locks are held for a specified duration, automatically expiring if not renewed or released.