Proposal : Out of the box support for distributed locks

I'll admit this might not be the best place to open the discussion but I couldn't find anywhere else.

Once upon a time we had Spring Cloud Cluster supporting Lock Registry which was deprecated into Spring Integration. Tell me if I am wrong but even if I add dependencies from Spring Integration it doesn't feel to me that it just works out of the box with the COC so dear to the Spring Boot phylosophy. We need to do a couple of plumbing to have something working out.

Distributed Locks for internal batches or croned services is a recurrent topic in my opinion in a distributed system. I would like to contribute to a starter module inspired by your sample Lock Server Demo. We have a starter server for Eureka and the Config Server. Why not treating locks as a first class citizen among the problems eased by Spring Cloud with a starter server project and a starter client.

I'll work on my own embeddable server and client but it feels to me that such feature would make sense to be part of the project.

Start by reviewing the sample Lock Server Demo and the Spring Integration Lock Registry mentioned in the issue, then compare them with the existing Eureka and Config Server starter projects. The issue does not name files, tests, or acceptance criteria; completion would require an agreed scope for starter server and client support.