Yeah the static stuff being fast is less surprising - it was mainly the search results page that astounded me.
> via served via spark[2]
Had not heard of this Spark (only the other Apache one). Will definitely take a look.
> Although the search engine is a bit on the slow side since it's routed through cloudflare and I think I'm relatively far away from the closest datacenter so it adds like 100ms to the load times.
I've hit the CF loading screen which introduces a big delay, but when I don't see that the loading is really instantaneous.
Yes, and it was not that well designed to be honest... the successor is quite a lot nicer and it's called Javalin[1].
Same philosophy but just got things right where Spark, being the "first" (in the Java world, using the design inherited by Sinatra[2]) had a few design issues.
For anything handling user input I'd be concerned about maintenance status for fixes. Even beyond the codebase itself, even just maintaining an up to date pom.xml can be important - seems theirs was last updated in July of last year. Very brief manual browse of it shows potential exposure to things like https://nvd.nist.gov/vuln/detail/CVE-2022-25647 - not sure if that's reachable in the codebase but there could be others.
Yeah the static stuff being fast is less surprising - it was mainly the search results page that astounded me.
> via served via spark[2]
Had not heard of this Spark (only the other Apache one). Will definitely take a look.
> Although the search engine is a bit on the slow side since it's routed through cloudflare and I think I'm relatively far away from the closest datacenter so it adds like 100ms to the load times.
I've hit the CF loading screen which introduces a big delay, but when I don't see that the loading is really instantaneous.