RE: Anaemic Domain Model

2017-08-30 Thread Narayana Rengaswamy
PM To: user@ignite.apache.org Subject: Re: Anaemic Domain Model With Scan Query there are no restrictions, you can filter on any level of nesting, with computed properties, etc etc. It is just a piece of your code operating on your object, so you can do anything. SQL is more limited

Re: Anaemic Domain Model

2017-08-30 Thread Pavel Tupitsyn
ither SQL Query, or Scan Query. > > > > Thanks, > > Narayana. > > > > *Narayana Rengaswamy* > > Optym – Live Efficiently > > M: +91-875-450-9770 > > > > *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] > *Sent:* Tuesday, August 29, 2017 8:08 P

Re: Anaemic Domain Model

2017-08-29 Thread Pavel Tupitsyn
Hi Narayana, Can you describe the difficulties that you have with storing rich model classes in Ignite? Anaemic domain model is controversial, opinions range from "good practice" to "anti-pattern". Ignite does not force you into any specific approach, IBinarizable a

Anaemic Domain Model

2017-08-29 Thread Narayana Rengaswamy
Hi all, I am using Apache Ignite (.NET) in a web application. My domain model classes are directly stored in Ignite cache, and I have persistence in SQL Server. I have DTOs to SQL Server, but none to Ignite. I can see that I am following an anaemic domain model due to several restrictions. I