그 Couchbase EF Core Provider is now generally available. This release brings the power of Entity Framework Core to Couchbase, allowing .NET developers to work with Couchbase using familiar EF Core patterns.
What is the Couchbase EF Core provider?
Entity Framework Core (EF Core) is a popular O/RM that simplifies database access for .NET applications. It allows developers to work with data using C# objects and LINQ queries instead of writing raw database queries. EF Core enables integration with various databases, providing automatic change tracking, transactions, and a familiar DbContext API. It’s a familiar interface that developers can use to save time and integrate with many frameworks and database-adjacent libraries.
그 Couchbase EF Core Provider enables developers to use Entity Framework Core with 카우치베이스 서버 그리고 Couchbase Capella (now available with a perpetual free tier). With this provider, you can work with Couchbase documents as if they were relational entities, using Linq queries, DbContext, and change tracking.
Getting started
To install the Couchbase EF Core Provider, add the NuGet package:
|
1 2 3 4 5 |
# .NET CLI dotnet 추가 package 카우치베이스.EntityFrameworkCore # Or using Package Manager Install-Package 카우치베이스.EntityFrameworkCore |
Example: using EF Core with Couchbase
Here’s a simple “shopping cart” example of how to set up and use the Couchbase EF Core Provider with a shopping cart model.
Define Your Entity Models
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
using 카우치베이스; using 카우치베이스.EntityFrameworkCore; using 카우치베이스.EntityFrameworkCore.Extensions; using 마이크로소프트.EntityFrameworkCore; using 마이크로소프트.Extensions.로깅; using 엔로그.Extensions.로깅; using ILoggerFactory = 마이크로소프트.Extensions.로깅.ILoggerFactory; 공공의 class Cart { 공공의 string CartId { 얻다; 설정; } 공공의 DateTimeOffset Created { 얻다; 설정; } 공공의 List<Item< Items { 얻다; 설정; } } 공공의 class Item { 공공의 string ItemId { 얻다; 설정; } 공공의 string 이름 { 얻다; 설정; } 공공의 uint Quantity { 얻다; 설정; } 공공의 decimal Price { 얻다; 설정; } } |
Create a DbContext for Couchbase
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
공공의 class CartContext : DbContext { 공공의 DbSet<Cart< Carts { 얻다; 설정; } 공공의 DbSet<Item< Items { 얻다; 설정; } private static readonly ILoggerFactory LoggerFactory = 마이크로소프트.Extensions.로깅.LoggerFactory.Create(builder =< { builder.ClearProviders(); builder.AddNLog(); }); protected override 무효 OnConfiguring(DbContextOptionsBuilder 옵션) { 옵션.UseCouchbase(새로운 ClusterOptions() .WithCredentials(“Administrator”, “password”) .WithConnectionString(“couchbase://localhost”) .WithLogging(LoggerFactory), couchbaseDbContextOptions =< { couchbaseDbContextOptions.양동이 = “Shopping”; couchbaseDbContextOptions.Scope = “Ecommerce”; }); } protected override 무효 OnModelCreating(ModelBuilder modelBuilder) { modelBuilder.Entity<Cart<().ToCouchbaseCollection(this, “Carts”); modelBuilder.Entity<Item<().ToCouchbaseCollection(this, “Items”); } } |
This arrangement assumes that you have created a bucket in Couchbase called Shopping, which contains a scope called Ecommerce, which contains collections Items 그리고 Carts.
Also, note that logging is optional, but it’s a good idea to turn it on to help identify any issues that may come up.
Insert and Query Data
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
await using 변수 db = 새로운 CartContext(); 변수 cart = 새로운 Cart { CartId = Guid.NewGuid().ToString(), Created = DateTimeOffset.Now, Items = 새로운 List<Item< { 새로운 Item { ItemId = Guid.NewGuid().ToString(), 이름 = “Widget”, Price = 0.99M, Quantity = 1}, 새로운 Item { ItemId = Guid.NewGuid().ToString(), 이름 = “Foo”, Price = 4.99M, Quantity = 3}, 새로운 Item { ItemId = Guid.NewGuid().ToString(), 이름 = “Baz”, Price = 99.19M, Quantity = 1} } }; await db.AddAsync(cart); await db.SaveChangesAsync(); 변수 items = await db.Items.Where(i =< i.이름 == “Foo”).ToListAsync(); foreach (변수 i in items) { Console.WriteLine(JsonConvert.SerializeObject(i)); } |
Here’s an example of what the documents in Couchbase will look like after insertion:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
Key: 080c210a–34eb–45ea–b9b4–e5c6f8afa4d6 { “CartId”: “080c210a-34eb-45ea-b9b4-e5c6f8afa4d6”, “Created”: “2025-03-13T17:16:31.9904224-04:00” } Key acf54397–51c4–4ad7–bf34–d0a42061b662 { “ItemId”: “acf54397-51c4-4ad7-bf34-d0a42061b662”, “CartId”: “080c210a-34eb-45ea-b9b4-e5c6f8afa4d6”, “이름”: “Foo”, “Price”: 4.99, “Quantity”: 3 } Key a3f25210–97f2–4c95–ad4b–f241dde0d9c3 { “ItemId”: “a3f25210-97f2-4c95-ad4b-f241dde0d9c3”, “CartId”: “080c210a-34eb-45ea-b9b4-e5c6f8afa4d6”, “이름”: “Widget”, “Price”: 0.99, “Quantity”: 1 } // … etc … |
What works in the GA release?
The entire functionality of EF Core is very, very large. Being able to handle every possible Linq statement, for instance, is nearly impossible, even for mature EF Core providers like SQL Server. However, this release supports many core EF Core capabilities, including:
✅ LINQ support – Translates LINQ queries to Couchbase SQL++.
✅ Basic CRUD operations – Insert, update, and delete work as expected.
✅ Change tracking – Entities are tracked for efficient updates.
Also note that using Async methods is required. Couchbase’s .NET SDK is completely asynchronous. If you try to use a non-async method, you will get a runtime error along the lines of Couchbase EF Core Database Provider does not support synchronous I/O.
Known limitations
While this is a significant milestone, some features are still a work in progress, including:
❌ Denormalization – Nesting collections inside documents (e.g., storing Items inside Cart as a single JSON document) is not yet supported.
❌ Eager Loading – .Include() statements may not work as expected.
❌ SQL++ Function Support – Some SQL++ functions like META, RYOW, etc., are not fully implemented.
❌ 거래 – Not yet supported in this release.
Join the conversation!
We want your feedback! Help shape the future of the Couchbase EF Core Provider:
- Ask questions and share experiences in the Couchbase .NET forums.
- Chat with us on Discord – Join our community.
- Report issues and contribute ~에 깃허브.
What’s next?
This release is just the beginning! We’re actively working on building out this EF Core implementation. Your feedback will help to prioritize functionality.
Try it out today and let us know what you think. Happy coding!
댓글 남기기
댓글을 달기 위해서는 로그인해야합니다.