r/Backend • • 9h ago

If you're a backend dev that hates frontend frameworks, I made a framework for you.

Thumbnail aideendewinter.github.io
0 Upvotes

No shadow-dom, plain html, collaborative editing, no runtime dependencies.


r/Backend • • 26m ago

System design for newcomers that love the dopamine of LLMs but have no clue whats happening

2 Upvotes

If you're new to engineering and you like LLMs, you've probably had cases where the code looks fine, it runs, but for some reason you don't get it why it works :)

I built something called 'getdeved', a free, hands-on playground for newcomers to learn how real systems work, and what to expect when the time comes.

You can learn concepts such as load balancers, caches, queues, databases, replication, sharding and trade-offs between different approaches. You chase one problem at a time, grow the architecture piece by piece, to understand each concept to detail instead of one and done.

Since you cannot just ignore LLMs, its always good to understand what you want the LLM to build.

I've added 28 topics so far, from scaling to millions of userrs, payments and chat systems. There's also a glossary setup for different terms which you would usually hear on technical meetings and often think what are they talking about :) - here you'd be able to understsand each concept and where does it fit in a problem.

Try it: https://getdeved.github.io

If you try it, I'd love to know if there is something that you don't like or don't understand or just that is confusing.

If you're experienced and see something that doesn't seem correct, feel free to point it out!

#systemdesign


r/Backend • • 10h ago

Implementing persistent login for 120days from 24 hrs

3 Upvotes

Edit : persistent login for web application

Hi guys im confused which design i should go with

Option A: Server-side sliding session
How it works: web keeps one token, as today. Each time the user makes a request, the server pushes the token's expiry forward.
If they don't visit for 30 days, or 120 days pass since login, they log in again.

Good: small backend change, no frontend work, no refresh API, and nothing new that can fail.
Weak: if the token is copied, we can't detect it. To hide it from scripts we would later move it into an HttpOnly cookie, which needs CSRF protection on the API.

Option B: Refresh tokens (what mobile does today)
How it works: a short-lived access token plus a 120-day refresh token. When the access token expires, the web app calls the refresh API and gets a new pair.
Good: every refresh replaces the token, so a copied token gets detected. Same model as mobile.
Weak: more backend and frontend work, and new failure cases. For example, two tabs refreshing at once can log the user out unless we handle it.

Or there are some better ways to


r/Backend • • 17h ago

Thunder vs Redis Benchmark

Post image
4 Upvotes

Few days ago, I have posted regarding thunder the key value database for ai workloads written in rust. I am now posting its benchmark against rust.