CRUD APIs are Poor Design
Typical API Design consists of building around database records and Create Read Update Delete. Making nothing more than a UI or HTTP API around a database. But that database schema was driven by business processes. But if those business processes don't live in your system, then trying to evolve your schema can be challenging. Instead of modeling data structure, model business processes and the data behind them. 🔗 EventStoreDB https://eventsto.re/codeopinion 🔔 Subscribe:    / @codeopinion  💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon   / codeopinion  ✔️ Join via YouTube    / @codeopinion  📝 Blog: https://codeopinion.com 👋 Twitter:   / codeopinion  ✨ LinkedIn:   / dcomartin  📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo... 0:00 "REST" 3:18 What do you say you do? 5:29 Extend 8:46 Model Business Processes

Solving the 'God Object' Problem with Shared Identity

Domain Modeling Gone Wrong - Part 1

System Design Explained: APIs, Databases, Caching, CDNs, Load Balancing & Production Infra

Why The Russian Accent Terrifies Everyone

I Don't Think I Can Go Back To Windows...

How to (and how not to) design REST APIs

System Design Course – APIs, Databases, Caching, CDNs, Load Balancing & Production Infra

Storchennest Live Webcam in Bad Salzungen, ThĂĽringen

Keep your project structure simple!

DTOs & Mapping : The Good, The Bad, And The Excessive

Ex-Google Recruiter Explains Why "Lying" Gets You Hired

Why Separate Databases? Explaining Like You're Five

What is a REST API?

Designing Data-Intensive Applications: Chapters 1 and 2

What makes an Aggregate (DDD)? Hint: it's NOT hierarchy & relationships

Want to build a good API? Here's 5 Tips for API Design.

🇩🇪 German industry JUST died (it’s WORSE than you think)

API Design in System Design Interviews w/ Meta Staff Engineer

Message Queues in System Design Interviews w/ Meta Staff Engineer

