It's code review and design time. Recently I recorded a video providing my thoughts on some code attempting to illustrate persistence ignorant for queries. I didn't cover some specific api design decisions that I didn't agree with around nullables and throwing exceptions. I'll show samples of what I'd prefer the API to look like and why.

🔗 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

DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Code Review & Refactoring to a better design