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... 😢
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... 😢
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!
Amazing video! I'll see it in a while
You touch on archiving, but I’d love to hear some examples!
Check out this video: th-cam.com/video/_zRXJuW7W98/w-d-xo.html
@@CodeOpinion omg this is perfect. Love your videos, I’m bringing them up in basically every engineering convo at my company