The latest articles on DEV Community by Anatoly Demidovich (@da440dil). https://dev.to/da440dil https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F210776%2F3082321e-9e42-4b22-abad-a25ddb0bdfa4.jpg https://dev.to/da440dil en Anatoly Demidovich Mon, 12 Aug 2019 08:52:22 +0000 https://dev.to/da440dil/distributed-locking-rate-limiting-bd https://dev.to/da440dil/distributed-locking-rate-limiting-bd <p>In one of my previous projects, I ran into two problems. And this is not <a href="https://martinfowler.com/bliki/TwoHardThings.html">cache invalidation and naming things</a> as you might think :). This is distributed locking and distributed rate limiting. In my opinion, I did a pretty good job solving these two. And now after some simplifying and reshaping I think the solutions are ready for publishing and here they are: <a href="https://github.com/da440dil/go-locker">go-locker</a> &amp; <a href="https://github.com/da440dil/go-counter">go-counter</a> on <a href="https://golang.org/">Go</a> and <a href="https://github.com/da440dil/js-locker">js-locker</a> &amp; <a href="https://github.com/da440dil/js-counter">js-counter</a> on <a href="http://www.typescriptlang.org/">TypeScript</a>. Comments are welcome.</p> node javascript typescript go