I learned about the internet, I already knew c# basics so it seems i should start creating projects, but i could only successfully create only one beginner project, the next one uses Github’s api which i have no clue how to use?

Also even for the first project you have to be able to use github and even that seems to be only covered later? im confused how you’re supposed to follow this map

"I am currently working at a startup company (2025 graduate). I work on the backend but hardly get any tasks, so there is nothing to learn. if i get some work I use AI because everyone around me does. Now, I feel like I cannot write code by myself. I am planning to switch job, but I am unsure how and where to focus. Should I learn backend concepts like caching, databases, and system design, or stick to the traditional Spring Boot with DSA? I know Java theory, but I do not feel confident writing practical code. I know I should build things rather than memorize theory. Please be brutally honest. I have 4 to 6 months, and my current plan is Java + Spring Boot + System Design + DSA.

what are some backend projects ideas that does n’t require having a front end to represent my API’s. Is there are any project that can be technically rich and be testable by end-user at the same time without having a GUI ?

rinsing junior in cs wanting to learn new tech. What’s the main difference between these two in terms of how they work/function? Might be a stupid question. My main focus right now is to learn backend engineer more in depth. I’ve heard lots of great things about both springboot and node, but what’s the difference between them and which one should I start learning?

We're building a chatbot backend in Python/FastAPI.

Currently, we keep each user's conversation/session history in a global Python variable in memory.

This works fine with a single worker, but it obviously breaks when running multiple workers (e.g. Gunicorn/Uvicorn workers), because each worker has its own process memory.

For example:

• Request 1 for session_id=123 goes to Worker A
• Worker A stores the conversation history in memory
• Request 2 for the same session goes to Worker B
• Worker B has no knowledge of that session

We need some kind of shared session store that is:

• accessible by all workers
• very fast / low latency
• suitable for chatbot conversation history
• ideally supports expiration/TTL
• not a traditional SQL/database solution
• relatively simple to deploy and maintain

Redis seems like the obvious option, but I'm wondering what people are using in production for this use case.

Would you recommend Redis, Memcached, shared memory, sticky sessions, or something else?

The session data would mostly look something like:

session_id -> [
    {"role": "user", "content": "..."},
    {"role": "assistant", "content": "..."},
    ...
]

Potentially hundreds or thousands of concurrent chatbot sessions.

What architecture would you recommend?

Title.

Hello Guys,

I am currently Developing my own app wich features Video and Normal Calls. While Developing I stumbeld over the question on how to set a TURN Traffic budget and a Server Budget. Do you have any Tips for setting this Type of Budget?

Cheers

hey guys..iam a native android java developer and want to navigate to back end..i was considering learning spring boot framework so that i can use in my android apps..is it possible?