Implementing CRUD and table relationships in .NET 8 with MongoDB and SQL

Data and Databases
1

Hey everyone,

I’m working on a project using .NET 8 and I need to connect to both MongoDB (NoSQL) and a SQL database. I’m kind of stuck on how to set up table relationships and perform basic CRUD operations.

Does anyone have a straightforward example they could share? I’m especially interested in:

  1. Connecting to both databases
  2. Setting up relationships between collections/tables
  3. Implementing Create, Read, Update, and Delete operations

I’ve tried looking at the official docs, but I’m having trouble putting it all together. Any help or code snippets would be super appreciated!

Thanks in advance for your help!

2

yo, i’ve done similar stuff. use mongodb.driver for mongo and ef core for sql. for relationships, embed docs in mongo or use refs. ef core handles sql relationships ez.

crud ops? just make repository classes for each db. keeps things clean. don’t forget error handling tho!

connection strings are key. set em up right in startup.cs and use dependency injection.

3

hey there! have u thought about using dapper for SQL? it’s super lightweight and fast. for mongo, the official driver is gr8.

what kinda relationships are u dealing with? i’m curious about ur data model. maybe we could brainstorm some ideas?

how’s ur experience with nosql so far? wanna chat more about it?

4

Having worked extensively with both MongoDB and SQL in .NET projects, I can share some insights. For MongoDB, I recommend using the official MongoDB.Driver NuGet package. It provides a fluent API for CRUD operations and supports complex queries. As for SQL, Entity Framework Core is an excellent ORM choice in .NET 8.

To establish relationships in MongoDB, you can use document embedding or references. For SQL, EF Core handles relationships through navigation properties. In my experience, the trickiest part is often managing transactions across both databases simultaneously.

For CRUD operations, I’ve found it beneficial to create separate repository classes for each database. This approach keeps your data access logic clean and allows for easier unit testing. Remember to implement proper error handling and consider using the Unit of Work pattern for managing multiple operations.

Lastly, don’t overlook the importance of proper connection string management and dependency injection setup in your Startup.cs file. It’s crucial for clean, maintainable code.