fuse VS reitit

Indeed. I do wish there were a few more "extras" in OTP, because "let it crash" needs some more details in some circumstances.

For instance if you have a system with a user interface and some various components, like say, a database, and the database becomes unavailable, you don't want the entire system to crash. You want it to display an error message to the user and maybe go into some kind of diagnostic mode or other "things are not normal" state.

Something like https://github.com/jlouis/fuse is one approach.

> If you configure it well (the defaults are not always optimal) you can have your invisible mesh of services survive extended outages of the 3rd party APIs it depends on.

This is something that annoyed me a bit with OTP. The basic strategies aren't really enough for that, so you need something like https://github.com/jlouis/fuse

I wrote something like that myself, but it hasn't seen a ton of use: https://github.com/davidw/hardcore

I would build the CLJS for your game logic. Then I would build the backend server separately with API endpoints your front end to talk to. https://github.com/metosin/reitit is a pretty good option.

A significant feature of reitit is that routes are composed of simple vectors and maps. That means you can pre-process that data structure however you want before building the router.

You might look at the examples on the Reitit page. Reitit seems to be the emerging library for routing, and it does get you most of the way there, no matter which direction you are looking to go..

for runtime validation & coercion, you can use the pedestal-utilities from reitit which support all of spec, schema and malli. For dev-time var instrumentation (static & dynamic), there are several ways to add those to existing or 3rd party codebases.