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 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.

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'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?

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 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 have competed the JDBC ORM and Hibernate and spring data jpa what should learn next

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 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?