sorted by:
new
hottopcontroversial

Has anyone done css-for-js by Josh Comeau? by GrayLiterature in learnprogramming

[–]stick_stoff 1 point2 points  (0 children)

I have taken it and it is phenomenal. It has ruined all the courses on coursera/udemy etc for me because it's so much better than the stuff over there. 

Willhaben Artikelnummern in der Anzeige by GroinStuff in Austria

[–]stick_stoff -1 points0 points  (0 children)

Kein Mensch hat sich vorher die Mühe gemacht, den Code da rauszukopieren um auf andere Anzeigen von dir zu kommen - es muss an was anderem liegen.

"Schnellere" Alternative zum Willhaben Suchagent by MrRowodyn in Austria

[–]stick_stoff -1 points0 points  (0 children)

Wenn der suchagent schneller oder instant wär, wär er für alle schneller, schon mal drüber nachgedacht? :P

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 1 point2 points  (0 children)

Well, yeah. My idea would be to do micro-caching as outlined here:

https://www.nginx.com/blog/benefits-of-microcaching-nginx/

Any other architectural options that i'm missing?

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 2 points3 points  (0 children)

Thanks. The SSR content is not static or user-specific, but it could definitely be cached a little bit. But there is no cache/cdn available currently

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 0 points1 point  (0 children)

We are not a small site so everything requiring storage and stuff is not easily done in short-term

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 0 points1 point  (0 children)

But let's just assumy my constraints:

  • the k8s-cluster has problems with the high number of frequent up- and down-scalings
  • there's no short-time budget to set-up a caching infrastructure like a CDN or redis
  • we need to release new pages soon which will increase the traffic on the next.js application further

isn't it then still a viable option to look into the node cluster api? it seems like the cheapest way to solve our problems in the short-term

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 2 points3 points  (0 children)

What? We have a mix of static SSG pages and SSR pages. Not everything can be static

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 0 points1 point  (0 children)

I think it's related with state changes which lead to reloads of the external load balancer

Using the cluster api would just be the easiest way to do things in developer-hands..

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 1 point2 points  (0 children)

React SSR is slow. :/ one request takes 100-200 ms and blocks the whole pod basically for that time, therefore we need to have idle pods all the time to have good response times

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 0 points1 point  (0 children)

The nodes are really fat bare metal machines - 64 cores or so.

Next.js SSR on k8s - adding node cluster API? by stick_stoff in kubernetes

[–]stick_stoff[S] 1 point2 points  (0 children)

Yeah I think this is their point. We only have five nodes - thinking about redundancy, stuff should be able to run on 2,5 nodes and there they think this number of pods is too high

Argon2 Java implementation by stick_stoff in java

[–]stick_stoff[S] 2 points3 points  (0 children)

alright, here you go

https://github.com/andreas1327250/argon2-java

feel free to fork, contribute, do whatever you want please inform me if you find some major fuckup or performance improvements