question on bringing a database in the mix in yada resources:

how would you manage a datomic database value in your resources? Let's say you need the db value in multiple interceptors (auth, properties, response). You probably want to insert an interceptor that updates the context before all that stuff happens?

or is the general advice to do this in 'properties'?

We establish the database value and assoc into the req context, using an interceptor precise because its used in auth. @stijn

makes sense. in our case we do auth with an external system, so assoc'ing it in properties is fine

If you want to know more about this interceptor, it's discussed in my blog article today: https://juxt.pro/blog/posts/live-programming-websites.html

https://twitter.com/juxtpro/status/824930169555148800

Retweets welcome!

really interesting read!

integrant's suspend / resume functionality got me thinking on the same line, where you can update e.g. your handler without restarting the webserver

one concern is, how can you guarantee everything still works when your server fails, the node dies, or becomes unusable and you have to restart everything from scratch?

I saw that. Really want to look at James's new stuff

@stijn component can do that via another library of his :)