Clojure

The “Library Locker” is a common anti-pattern for incorporating third party libraries into an application. The application wraps the library with its own function, which mixes concerns and makes the library more difficult to use. In this article, we will first consider the original problem the library locker is introduced to solve, then an example of the library locker, and then suggest better alternatives. The Problem Suppose we have system of microservices that support astronomical applications. We locate our calls to our other microservices in a service directory. ...

This is the first in a multi-part series, “Brittle Clojure”. In this series, we will consider common patterns in Clojure which yield brittle systems, as well as methods to ensure robustness. None of the basic principles for building robust software are unique. Most literature, however, is focused on object-oriented systems. Our point of view will sometimes zoom in to Clojure “in the small”, and sometimes zoom out to distributed systems built with Clojure. ...