You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/11/05 13:07:59 UTC

[jira] [Assigned] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache

     [ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov reassigned IGNITE-1915:
---------------------------------------

    Assignee: Pavel Tupitsyn  (was: Vladimir Ozerov)

Pavel,

Implementation looks good to me. However, I strongly suggest to perform another review with someone who has strong experience in distributed algorithms. E.g. w/ [~sboikov] or [~agoncharuk].

Vladimir.

> .NET: Ignite as Entity Framework Second-Level Cache
> ---------------------------------------------------
>
>                 Key: IGNITE-1915
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1915
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .net, roadmap
>             Fix For: 1.8
>
>
> Entity Framework is #1 ORM for .NET
> We should provide easy solution to boost Entity Framework performance with Ignite.
> EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in one, EF6 requies more customization or a 3rd party lib like https://efcache.codeplex.com/). For now, let's do EF6 only.
> This should be in a separate assembly and a separate NuGet package.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)