An approach to “restating” an Excel workbook as executable Clojure code in order to verify its calculations; test those calculations against known inputs; compare it with previous versions; and potentially provide a path to retiring the Workbook as executable content, reducing the operational risk of exclusively positioning Excel at the core of important business processes.

For long-running server processes possibly initiated by an AJAX call from an SPA client, it’s often desirable to be able to receive (and display) status update messages (issued by the server during processing) in your front-end application’s UI. In this piece I will discuss the two options of using websockets and SSE (server sent events), and, with code, show how to implement them using Clojure and ClojureScript.

I discuss the available backends available in the buddy-auth library and how they are implemented. I will then show, for circumstances where the provided back-ends don’t meet our needs how we can implement our own.

In this piece I will cover briefly how the Pedestal web-server operates, particularly the interceptor model and error handling; how to integrate a Pedestal web application with the buddy-auth library; and I will demonstrate with code how to secure access to Pedestal endpoints using the buddy-auth library.

I will show you how to deploy a packaged application comprising a Clojure Pedestal API server and a ClojureScript (reagent/reframe) front-end React application to a Kubernetes Cluster running on GKE (Google), and how to make it available externally at a specific URL.