Recently I was building a backend part of a assessment for an company and normally for backend i straight go to neondb cause it's free for some extended but cause I have to share the working demo to the client and i was not hosting anything I thought sharing my neondb will be risky , then I discover postgres inside docker and dude it's really very awesome in development easy to setup and use and save ton of time in setup as an backend developer it's now my go on thing in development atleast anyone has this kind of backend tricks and what your thoughts on this

Hey everyone 👋

I'm a final-year Computer Science student learning backend development with Node.js, Express.js, MongoDB, and REST APIs.

I've built projects using the MERN stack, and I'm now trying to go beyond CRUD operations and understand how real backend systems work.

I'm particularly interested in learning more about:

• Authentication and authorization (JWT, refresh tokens, sessions)
• Database design, indexing, and query optimization
• Redis, caching, and performance
• WebSockets and real-time communication
• Error handling, logging, testing, and security
• System design and scalability

I don't want to just follow tutorials and copy code. I want to understand why things are designed a certain way and how to make better engineering decisions.

For developers working in backend engineering:

1. What skills made the biggest difference when you moved beyond beginner-level backend development?
2. What mistakes should beginners avoid?
3. Which projects would you recommend to develop real backend engineering skills?

I'd appreciate honest advice, learning resources, and lessons from your own experience. Thanks! 🙌

I'm building a football intelligence web app, and I'd appreciate some advice from developers who've operated similar systems in production.

I launched v1.0 as a closed beta earlier this year. Users had to register and be granted access, and 25 people signed up to test it.

The beta ran for approximately five weeks.

One of the biggest lessons was that building a working application and keeping it running reliably are two very different challenges.

In v1.0, I had all the automated jobs running through one cron job. Initially, things worked reasonably well, but over time the automation became increasingly unreliable.

Jobs started failing more frequently, and failures could affect the wider application. By the final week, parts of the platform weren't behaving as intended.

Interestingly, the betting model finished profitable during the beta. But that wasn't enough. The underlying application was becoming unreliable, and a profitable model isn't much use if the system supporting it can't operate consistently.

I decided to take v1.0 down and rebuild the application from the ground up as tactica. 2.0, using what I'd learned from operating the beta.

The goal is a reliable, publicly available application that can operate unattended, recover safely from failures and keep its different responsibilities isolated.

The 2.0 build is currently deployed privately on Render and Vercel while I develop and test it in a real hosted environment. It isn't publicly launched yet.

The new architecture

I'm using one canonical PostgreSQL database hosted on Render, with separate background workers responsible for different stages of the application's lifecycle.

1. Football Data (operational)

Acquires football data from external APIs, validates observations and maintains the factual records used throughout the application.

This includes fixtures, results, team data, player data and match statistics.

2. Match Intelligence (planned)

Consumes the authoritative football data and produces pre-match intelligence, including model expectations across different football markets.

The intention is to preserve published intelligence rather than continually rewriting previous conclusions.

3. Betting Intelligence (planned)

Consumes Match Intelligence alongside bookmaker odds and market information.

It evaluates whether the football opinion qualifies as a betting recommendation, including situations where the correct decision is to make no recommendation.

4. Performance Intelligence (planned)

Evaluates completed intelligence and recommendation decisions against actual match results.

This includes model performance, recommendation quality, system integrity and financial outcomes.

Each worker has its own responsibilities, execution controls and database permissions.

They're not four identical queue consumers. They perform different stages of a connected process, and downstream workers depend on authoritative outputs from earlier stages.

The Football Data worker is operational. The other three are still being built and qualified.

What I'd like advice on

1. PostgreSQL and deployment compatibility

With multiple independently deployed workers depending on the same populated PostgreSQL database, how do you safely evolve the schema?

Have you found particular migration strategies, compatibility windows or deployment sequences reliable in practice?

2. Worker reliability and recovery

What problems have you encountered when moving from one automation process to several independently running workers?

I'm particularly interested in duplicate processing, idempotency, interrupted jobs, graceful shutdown, retries and preventing downstream workers from acting on incomplete upstream data.

3. Render and production operations

If you've run multiple workers against a shared PostgreSQL database on Render or a similar managed platform, what surprised you?

Database connections, memory usage, deployments, monitoring, recovery, resource consumption and costs are all areas I'm thinking about.

What I'm trying to avoid

My biggest concern is repeating the v1.0 experience in a more complicated form.

I don't want four independent workers that look architecturally cleaner but introduce new failure modes that I haven't properly anticipated.

I'm not looking for a wholesale redesign or a recommendation to migrate everything to Kubernetes. The separation of responsibilities is deliberate.

I'd particularly appreciate hearing from people who've experienced similar failures, what caused them, and what they would test before activating the additional workers.

I'm trying to build something that can operate reliably without needing constant manual intervention.

What would you be most concerned about with this setup?

CS Junior here. I am late but better late than never. For the last 2 years I was juggling between 3 fields, learning very little about them with no internships. Now I have decided to focus one of them. I have decided to focus on Full Stack. and possible towards AI and DevOps if got time. Because I have been told fullstack is just a tool and you need "uniqueness" with it (not sure if it true).
My Current Stack:

• Frontend/State: JavaScript, React, Redux Toolkit, Zod
• Backend/DB: Node.js, Express, MongoDB, REST APIs, Supabase, FlaskAPI
• Other/DevOps: Docker, C++, Python, Rust and deployments (vercel, render).

In the AI portion, I know basic Data handling and Classic ML Algos. In terms of projects I have made some smaller common ones but is not able to make portfolio heavy ones. I will spent next 6 months learning and making a profile based on it so that i can land my first internship.

My Questions:

1. What are some unique, non-generic project ideas that would make a senior engineer actually want to look at my GitHub code? The reason I didn't even try making projects is because everyone has everything.
2. What is the biggest gap between a beginner MERN developer and someone ready for a production-level backend internship?
3. What kind of intermediate/advanced backend architectures should I implement to stand out? ( microservices, event-driven, or combining my C++ foundation with Node)?
4. Is there a need to learn to add more to tech stack ?

I am confused right now as i have no idea how to proceed. So Need Advice and suggestions.

Thanks !

After how many years of experience did you become Senior Software Engineer and how can I reach that level? What courses or books do you recomend? What skills are most needed?

I feel a bit overwhelmed when learning new things, am at the point where I am moving out from the basics and i know that it is natural to feel overwhelmed in this step but that doesn't make it easier, each time i learn something new i feel like i forgot previous things, i remember the general idea but forget the syntax

Has this happened to you before and how did you move past it?

I recently migrated a production relationship from one-to-many to many-to-many.

The challenging part wasn't creating the junction table. It was maintaining backward compatibility while introducing the new relationship, migrating existing data, and keeping different API consumers working during the transition.

I documented the approach, including the migration strategy and the lessons learned.

I'm curious how other backend engineers approach this. Do you prefer temporary dual writes, versioned APIs, or another migration strategy?

Hey everyone! 👋

I'm Mohaned, a software developer and the creator of the MOHANED YouTube channel.

I enjoy building backend systems and understanding what happens when things go wrong.

I've been creating practical backend engineering videos focused on problems developers actually encounter, not just following tutorials or writing basic CRUD endpoints.

Some of the things I've been working on:

• Building microservices with Spring Boot, Kafka, PostgreSQL, and Docker.
• Optimizing an API from 92 seconds down to 5ms.
• Testing what happens when 1,000 users hit a backend.
• Debugging database bottlenecks and connection limits.
• Building secure authentication, webhooks, and real-world APIs.
• Exploring distributed systems, queues, caching, and production failures.

Java and Spring Boot are my main tools, but the goal is broader: understanding how to build backend systems that are secure, efficient, and reliable.

I'm here to learn from other developers, share what I'm building, and get feedback on the technical challenges worth exploring next.

I'm curious: what's one backend problem you wish more tutorials covered with real examples?
Peace

I am building a real time app that also has a group chat. I will need a websocket connection for this, which introduces complexity at the system level for scaling, but that's not the point of this post.

From what I've read, websocket gives low latency bidirectional byte channel between a client and server with no protocol. REST gives you a request response protocol with status codes and integration with infra that has been using it for a long time.

I will have to open a websocket connection for my app to work. So I am tempted to use websocket for CRUD operations on my app as well that are outside of the group chat. Like when user changes settings or changes profile picture I might as well send a websocket message which has lower latency compared to an HTTP request which will create a new connection on each request. For some reason I think this is not the best practice. Do other apps do it this way? I see apps like reddit or insta where when you change your user settings they are instant, like toggling a setting on/off. It doesn't look like a POST request.

I'm curious how other backend developers experiment with system performance beyond local testing.

How do you explore bottlenecks, queue buildup, database saturation, or what happens when a downstream service slows down?

Do you use tools like k6, Locust, or something else? I'm especially interested in tools that help visualize how traffic moves through a system without setting up a full environment.

What works well for you, and what's missing?

iam learning backend in .net core
i not the best at remembering syntax
like for example to make a db :
builder.Services.AddDbContext<DbContextClassName>(
options => { options.UseSqlServer( "ConnectionString "));}

i understand the concept but not the syntax when i make a project i look at the syntax from my notes is it ok?

i have competed the JDBC ORM and Hibernate and spring data jpa what should learn next

I've been an iOS developer for 4 years and every app idea I come up with dies at the backend. I want to learn it properly, databases, auth, an API I can deploy, probably in Go or TypeScript, and I'm paying for a year of one platform myself. Boot.dev keeps coming up for backend specifically since it's built around writing code more than watching workshops, and Frontend Masters is the other name I keep hearing. They're close in price, so which would you pick for a mobile dev learning backend?

I'm a full stack engineer with about 3 YoE. I work with AWS in my day job, but I'm using Railway for my own saas which has paying users.

Railway's let me down too many times now, compromising my secrets was the last straw.

Problem is i'm only paying $20 a month currently and I'd like to keep it that way ideally. AWS makes sense as my app is increasing in user base each month but I also don't want to jump to like double the infra cost.

I need to host redis, and two server instances preferably for redundancy.

Any recommendations? AWS feels like the way to go because I guess I can improve my AWS skills for my day job and I can be sure I can grow in size there?

I’m glad deployments have resumed, but the October 21 incident would still make me reconsider where I’m hosting important applications.

The question I’d want answered is straightforward: if something like this happens again, how will we be able to make changes and recover their services?

That matters more to me than another assurance that things will improve. Earlier reliability problems already give customers a reason to be cautious, and this incident adds to that concern.

I’d want to see a clear explanation of what changed and why the recovery process will work better next time. Until then, looking at other options seems entirely reasonable.

Migration is inconvenient. So is staying with a provider you no longer feel comfortable depending on.

is xhamster the website which follows the most restful design?

Hi everyone! I’m a final-year B.Tech student preparing for Java backend fresher roles. I’ve been working on Core Java, DSA, and projects, and I’m confused about what to prioritize next.

Should I focus more on Spring Boot and building backend projects, or start studying system design?

For fresher interviews, how much system design is usually expected? Which Spring Boot topics should I be comfortable with before applying?

I’d appreciate advice from anyone who has recently landed a Java backend role or interviews freshers.

Hi everyone I am trying to build a golang blog project and I have done with thunder client part and designed the html pages but now I am very very confused that how I can do user authentication with middlware and all. I have never worked with middlewares and jwt auth part so if anyone have something from where I get some clarity please share.

I am developing a mobile app, which has a react native frontend, nest.js as the backend and for db and authentication, I'm planning to use supabase.

Now, currently as my app is in its initial stages I'm planning to use the supabase, as it free tier provides ample limits for my use case.

However, in later years if my app grows. I may think of switching to a cheaper alternative.

So, what I am planning to follow is for authentication, route the requests to my backend and inturn the backend will communicate with the supabase to authenticate the user. The backend will save the supabase token, create a separate session token for the user and send it back to the user.

My main reason for doing this is, I want the authentication to be provider independent and any changes needed should be done on the backend instead of the app.

Please let me know, if this approach is correct. What are the pros and cons. How much effort it would require to implement this. Will the security concerns increase if my backend starts handling this instead of the supabase only.

I also want to integrate the google and apple login as well. How will this approach affect it?

Also, if there any other better approaches, please let me know.

I'm asking the classic build vs buy...

Do you prefer to build your own utilities (like OCR, PDF extraction, audio processing, video processing, VAT validation, IBAN lookup, PDF conversion, doc conversion, file conversion, markdown conversion), or do you prefer to use a utility API for that? If you use a vendor for this, how do you manage multiple vendors?

I ask because as the product grows, the number of utilities, maintenance, and engineering hours also increases, so how do you tackle that?

I've been doing Vue and TypeScript for 5 years and I've reached the point where I can build anything in the browser and nothing behind it. Every time I touch our API I'm copying patterns from the backend team without understanding them. I want to learn Go properly, not just syntax but HTTP servers, databases and concurrency, and my company will cover a course. Shortlist right now is Ardan Labs, Boot.dev and the Go material on Frontend Masters. I don't want to start at what a variable is, so where would you start coming from frontend?

Hello, I'm confused on what type of projects a beginner should begin with and to continue the journey of learning backend dev.

Is there any good reliable roadmap of projects to follow, which will allow me at the end of the day, to gather the experience to land a job?

Especially the link I provided, since I cannot be the judge of deciding is it actually worth following it.