[
https://issues.apache.org/jira/browse/IGNITE-22132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-22132:
----------------------------------------
Fix Version/s: 3.2
(was: 3.1)
> .NET: Thin 3.0: EF Core provider
> --------------------------------
>
> Key: IGNITE-22132
> URL: https://issues.apache.org/jira/browse/IGNITE-22132
> Project: Ignite
> Issue Type: Epic
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> EF Core provider will allow using Ignite as any other DB supported by EF.
> This makes adoption incredibly easy for the users - a matter of a few changed
> lines to switch from Postgres/MsSQL/MySQL, keeping all existing code.
> h2. But we already have a LINQ provider, what is the difference?
> Think micro-ORM vs full-blown one.
> *Ignite LINQ provider:*
> * Comes in the box, very lightweight
> * Can do LINQ without any setup, literally one line
> * Limited DML
> * No DDL
> *EF Core:*
> * Separate package
> * Full-blown ORM, extremely powerful
> * Familiar to any .NET developer, same API for many databases
> h2. More Info
> * EF Core is the most popular ORM for .NET. Provides an abstract way of
> working with a database without writing any SQL by hand. Includes DDL, DML,
> migrations.
> * Providers exist for many databases:
> https://learn.microsoft.com/en-us/ef/core/providers/
> * Writing a provider:
> https://learn.microsoft.com/en-us/ef/core/providers/writing-a-provider
> * Reference implementation:
> https://github.com/dotnet/efcore/tree/main/src/EFCore.Sqlite.Core
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
