Backend
27 articles in this category (Page 1 of 2)
Your API Doesn't Need Versioning
The default approach to API design is to prefix routes with version numbers like /api/v1/ and /api/v2/. In practice, route versioning leads to massive code duplication, client migration paralysis, and complex routing tables. Designing backward-compatible APIs is a much better operational model.
Why MongoDB is Still the Wrong Choice for 99% of Projects
The 'schemaless' pitch of document databases promised database flexibility and rapid iteration. In reality, your data always has schema. Moving schema constraints to the application layer leads to data drift, write corruption, and slow queries. PostgreSQL is almost always the correct answer.
Rust is Great, but You're Probably Using it for the Wrong Reasons
Rust is the darling of the systems programming world, boasting safety and performance without a garbage collector. But rewriting your company's simple HTTP CRUD API in Rust is likely a waste of time and money. Here is why the productivity hit of Rust is rarely worth it for typical web applications.
Why ORMs are the Worst Anti-Pattern in Modern Backend Development
Object-Relational Mapping (ORM) tools promise to free developers from SQL. In exchange, they introduce the N+1 query problem, hide database performance realities behind black-box abstractions, and create models that couple application state to database schemas. It's time to write SQL again.