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: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon https://www.patreon.com/codeopinion ✔️ Join via YouTube https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join 📝 Blog: https://codeopinion.com 👋 Twitter: https://twitter.com/codeopinion ✨ LinkedIn: https://www.linkedin.com/in/dcomartin/ 📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion 0:00 "REST" 3:18 What do you say you do? 5:29 Extend 8:46 Model Business Processes

CRUD APIsoftware architecturesoftware designcqrsdesign patterns.netmicroservicesmessage queuesevent driven architecturemicroservice architecturedomain-driven designenterprise service buscrud api using spring bootcrud api htbcrud api javacrud api reactjscrud api in react jscrud api java spring bootcrud api fluttercrud api postmancrud api gocrud api djangocrud api restcrud api reactcrud api useing spring boot