Help me with my stack...
Hi folks,
I'm prototyping a website for scores for a niche sport I play. The current popular one is some 2005 era wordpress monstrosity. This one will be nice and simple - display events, teams, players, scores, blog, news, and standings.
Because of the nature of the site, there will be many pages (thousands eventually) that will change quite regularly, so I'll need to SSR. However most of the requests will be for stale data (think people refreshing the score page many times) so I'm thinking I need a solid way to cache results, either in a CDN or serverside db, in order to keep costs low (it's out of my own pocket) and also to keep the site fast.
I'll need localisation as well, curling is played all over Europe as well as in Canada. And I want to use deno for the backend.
I was thinking of a few options
1. Astro frontend with the deno adaptor, deno backend, some DB (ps, cockroach, supabase). Hosted on Deno deploy or netlify. Cloudflare CDN managing the cache through a worker.
2. Astro frontend hosted on netlify with a redis/sqlite cache.
3. Just suck it up and use Next.js on vercel with ISR, with a deno backend hosted anywhere.
Anyone have some recommendations or suggestions? Cheers
16 Replies
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
lol
I’d use 3. With redis
If I'm using redis I don't need isr though no?
Well im junior to recommend. BUT you might cache the page inside redis and then regenerate it when its too old. So its like your own ISR.
The redis’s feature where the record has expiration time will come handy
why not just use next isr?
You said you had “unrelated issues to not use next”
yeah but option 3 is to use next 😉
I get your point tho. redis looks interesting
Oh yeah first I wrote 3, then read “not next” and started pitching 2
fair nuff
have you used redis in this usecase before?
why not ultra? @benten
not stable enough for something meant for production
i love ultra and it would be perfect for it otherwise
if you want something stable i'd use next or remix
remix with cdn seems perfect for this tbh
and with remix you can deploy the whole thing to cloudflare workers
or fly.io
Yeah i'm leaning towards remix behind a cloudflare cdn
which will let me purge specific routes from the cache through a worker like isr
the site would really benefit from progressive hydration (yuck can't believe I'm even saying that)
lmao
Lol.
Remix + cloudflare sounds interesting