[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306503#comment-15306503 ]
Pavel Tupitsyn commented on IGNITE-1915: ---------------------------------------- We need an efficient way to invalidate cached results, which means removing Ignite cache keys that match a condition. Options are: * ScanQuery. However, it will return entire CacheEntry to the calling node, and we only need the key. Value can be quite large (query result can contain hundreds of rows). * SQL. Downsides are that we have to enable indexing (less flexibility for the user), and SQL can't act on string[], we'll have to concatenate entity sets name * Compute: there are problems with guarantees * EntryProcessor: no way to iterate over ALL keys in cache Our best bet is to wait for IGNITE-2546 here. > .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 > > 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)