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] [Comment Edited] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
Date Tue, 23 Aug 2016 14:41:20 GMT

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

Pavel Tupitsyn edited comment on IGNITE-1915 at 8/23/16 2:40 PM:
-----------------------------------------------------------------

Considerations:

1) Introduce multiple caching strategies, similar to Hibernate:
* Read-only. Very simple, the fastest. No invalidation.
* Non-strict read-write. Only one writer is expected at the moment.
* Strict read-write.

We can implement strict read-write strategy as a separate ticket.

2) Get rid of EFCache dependency and implement the boilerplate ourselves. This will allow
more control over query execution.


was (Author: ptupitsyn):
I think we should introduce multiple caching strategies, similar to Hibernate:
* Read-only. Very simple, the fastest. No invalidation.
* Non-strict read-write. Only one writer is expected at the moment.
* Strict read-write.

We can implement strict read-write strategy as a separate ticket.

> .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: Vladimir Ozerov
>              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)

Mime
View raw message