Fork me on GitHub
#portkey
<
2020-03-09
>
viesti08:03:04

mentally playing with an idea on reitit route data -> API GW + handlers to Lambdas... (maybe have :target keyword on route data for specifying the type of lambda, like jvm, or graal...)

viesti08:03:17

to have fast local playground and the deploy to cloud

viesti08:03:31

just on thought level currently

baptiste-from-paris08:03:23

I am a little lost with reitit compared to other routing libs, any help ?

viesti08:03:17

it represents routes as as via nested vectors, then has ways to compile the routes into fast dispatch via the url path. The leafs of routes can have data attached to them to describe middleware, endpoint handler etc.

viesti08:03:49

Tommi has spend effort on making the dispatch fast

baptiste-from-paris08:03:15

compojure was not good enough ?

viesti08:03:25

reitit can also be used on the frontend, there's a core lib and then bindings to other stuff

viesti08:03:38

compojure is macro heavy, no inspection possible and the standard route matching is O(n) (walks the routes one by one to match for the url path/method)

cgrand09:03:11

and does weird things where it traverses twice to conditionnally apply middlewares

viesti08:03:17

not saying that don't use compojure, just that there are differencies 🙂