ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
Date Mon, 29 Aug 2016 14:22:20 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446014#comment-15446014

Pavel Tupitsyn commented on IGNITE-1915:

New design:
* Two mappings in a single cache: SQL+versions->results, EntitySet->version
* On each EntitySet update, increase the version with EntryProcessor
* On Get see if there is a key with current versions

This way the logic is very simple, and there is no need for locks or transactions. If the
cached data gets old, we just don't find it.

Old entries should be purged in background with something like IgfsDeleteWorker. We'll need
to start this worker on all nodes, regardless of platforms presence.
Special cache (IGNITE-3796) is needed to discover EntityFramework cache names.

> .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

View raw message