Clojurians Log v2

I think it's perfectly OK to use whatever middleware including Reitit middleware that makes sense in your application. What I'm arguing for is that you should use the same set of middleware if you want to achieve the 'uniform interface' constraint of REST. The set of middleware I'm proposing in the talk and rest.guide is designed to be used together, in a particular order, to achieve conformance. I'll try to specify the 'rules' for each step so it's clear what the semantics are of each step. That will make it easier to replace parts of the chain with other middleware.

@tkjone ^

yada is only getting critical fixes, at least from me - and I'm not 100% certain of the maintenance status these days of aleph. If it's working great for you I'm sure it will continue to do so - http is a slow moving tech. Presumably you are extending yada yourself for security headers, etc.

Makes sense. aleph has been moved to clj-commons

Part of the reason I've been working on a new collection of projects is so that I don't make substantial changes to yada and break stuff accidentally.

I think we will keep using it as it's working well for us. Rewriting to something else wouldn't really justify solving a real problem that we have, even for a new similar big project.

Gotcha. Makes sense. Thanks, Malcolm!

We want to add integration for ElasticSearch APM with yada. But there are some difficulties: APM couples a transaction to a thread it seems and yada requests/responses can be handled on different thread. Has anyone else done this?

Perhaps @dominicm?