Tips for Production Ready Database (Query) Design
Вставка
- Опубліковано 9 лип 2024
- When you're writing code for a new feature involving a database, you can fall into the trap of not realizing the volume of data the code you're writing will interact with in a production database. The amount of data you're local or development machine just differs from what will be in production. Especially years from now. Here are some things to consider when designing and developing to keep queries running quickly so they don't bog down your production system over time.
🔗 EventStoreDB
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 UA-cam
/ @codeopinion
📝 Blog: codeopinion.com
👋 Twitter: / codeopinion
✨ LinkedIn: / dcomartin
📧 Weekly Updates: mailchi.mp/63c7a0b3ff38/codeo... - Наука та технологія
Want to learn more about software architecture and design? Join thousands of developers getting weekly updates!
🚀mailchi.mp/63c7a0b3ff38/codeopinion
The only way to develop like production, is to have actual production data, something that will break any customers contracts, and if you sanitize the data, it's not like production anymore, like some SQL join thing that breaks only for that one user with a Turkish name... 😢
Amazing video! I'll see it in a while
video topic request: patterns for authorization and permissions, related to CQRS?
love these videos. :)
Good suggestion
Also statistical/log data should have the composite key "ISO 8601/Timestamp" + "Identity (long)" to align the data perfectly for reads.
Good and insightful video. Thanks
Glad it was helpful!
You touch on archiving, but I’d love to hear some examples!
Check out this video: ua-cam.com/video/_zRXJuW7W98/v-deo.html
@@CodeOpinion omg this is perfect. Love your videos, I’m bringing them up in basically every engineering convo at my company