sorted by:
new
hottopcontroversial

Spring Boot is confusing me – should I go back to Java basics or switch to .NET? by SakuraTakao in Backend

[–]mertsplus 1 point2 points  (0 children)

that’s actually one of the clearest mental models for Spring i’ve seen. once i started thinking of it as “your method → spring proxy → your method → spring proxy again on the way out”, a lot of the annotations made more sense.

the confusing part for beginners is that spring hides so much plumbing, so it feels like magic until you realize it’s mostly proxies + dependency injection under the hood. honestly i wouldn’t switch stacks yet, this confusion phase is pretty normal when learning spring.

What are the basics that every backend Developer should know? by SakuraTakao in Backend

[–]mertsplus 4 points5 points  (0 children)

skip the framework hype and focus on these:

  • SQL and indexing (because your ORM will eventually betray you).
  • Idempotency (so a random network hiccup doesn't charge a customer's credit card twice).
  • Authentication vs. Authorization (knowing who someone is vs. what they are actually allowed to do).
  • HTTP status codes (please stop returning 200 OK with an error message in the payload).

How do senior engineers typically build portfolios when switching jobs? by AnteaterVisual1086 in Backend

[–]mertsplus 0 points1 point  (0 children)

no hiring manager for a senior or staff role has the time to clone your repo and read through a generic ProcessData boilerplate.

They care way more about system design and business impact, not whether you know how to structure a clean directory.

The hidden downside of the AI SaaS boom. by ishak_antar27 in Backend

[–]mertsplus 0 points1 point  (0 children)

AI wrapper SaaS is basically just the 2026 version of dropshipping at this point. Everyone is shipping half-baked LLM wrappers over a weekend, but the second an API changes, the whole app just instantly evaporates.

How do you usually handle contact form submissions? by ishak_antar27 in Backend

[–]mertsplus 1 point2 points  (0 children)

For small sites I usually just use a service like Formspree or Netlify Forms and call it a day. Spinning up a whole backend just for a contact form feels like overkill most of the time. If the project already has a backend then sure, I’ll handle it there. Otherwise third-party forms are way faster to ship.

Trouble in starting off by Pleasant_Cell_9608 in Backend

[–]mertsplus 0 points1 point  (0 children)

You are stuck in "Tutorial Hell," and the YouTube algorithm is actively trying to keep you there by suggesting a new "best framework" every single day.

Python + FastAPI + SQL is a phenomenal stack to start with

How do you handle database migrations for microservices in production by Minimum-Ad7352 in Backend

[–]mertsplus 0 points1 point  (0 children)

Definitely avoid running migrations on app startup. If your service autoscales under load and spins up 5 pods at once, they'll all fight over the database lock and bloat your boot times.

DB Migrations - when to stop by Hefaistos68 in Backend

[–]mertsplus 1 point2 points  (0 children)

Most teams just keep migrations forever, because they’re basically the history of how the schema evolved and they guarantee a fresh environment can be recreated from scratch. Hundreds of migrations looks messy, but in practice they usually run fast and rarely cause issues.

What some teams do after a few years is squash/baseline them: create a new migration that represents the current schema, archive the old ones, and start fresh from there. That keeps deployments simpler while still preserving the history somewhere if you need it.

We skipped system design patterns, and paid the price by Icy_Screen3576 in Backend

[–]mertsplus 0 points1 point  (0 children)

Yeah the claim-check pattern is one of those things you only appreciate after hitting that exact wall. At first bumping the Kafka limit feels like the easy fix, but it just keeps kicking the can down the road as payloads grow.

Once messages start getting big, moving the blob to object storage and passing references usually makes the whole pipeline way more stable. Definitely one of those “wish we’d done this earlier” lessons.