C++ and .NET

[dsetrakyan]

Hi Igniters,

Last week GridGain has agreed to donate its C++ and .NET implementations
for Apache Ignite to ASF. This is big news, as now Ignite will be able to
add value to C++ and .NET communities. Together with Node.JS client, which
is under development, this creates a fairly large Ignite ecosystem.

These are not basic client APIs, but rather is a full-blown in-memory data
fabric for .NET and C++ users. The goal is that users of these languages
will not have to write any Java code at all in order to use any Apache
Ignite features. For example, .NET users will even be able to execute C#
closures over Apache Ignite runtime.

For the next couple of weeks GridGain will be working on migrating and
contributing the code and documentation to Apache Ignite. My hope is that
it will get into 1.4 release (assuming that release gods smile upon us).

D.

[nivanov]

I'm already grinning from ear to ear so release should go as planned :-))
Awesome news for sure.

As a side historical note: Dmitriy (Setrakyan) and I worked on our 1st
cross-platform (Java/.NET) in-memory middleware back in 2001-2002. Back
almost 15 years ago we saw a clear need for Java and MSFT-world to be able
to work together on in-memory computing middleware. It's immensely
gratifying that ASF gets a in-memory computing software (as part of Apache
Ignite) that delivers on that idea.
--
Nikita Ivanov


On Mon, Aug 17, 2015 at 5:26 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Hi Igniters,
>
> Last week GridGain has agreed to donate its C++ and .NET implementations
> for Apache Ignite to ASF. This is big news, as now Ignite will be able to
> add value to C++ and .NET communities. Together with Node.JS client, which
> is under development, this creates a fairly large Ignite ecosystem.
>
> These are not basic client APIs, but rather is a full-blown in-memory data
> fabric for .NET and C++ users. The goal is that users of these languages
> will not have to write any Java code at all in order to use any Apache
> Ignite features. For example, .NET users will even be able to execute C#
> closures over Apache Ignite runtime.
>
> For the next couple of weeks GridGain will be working on migrating and
> contributing the code and documentation to Apache Ignite. My hope is that
> it will get into 1.4 release (assuming that release gods smile upon us).
>
> D.
>

[Gianfranco Murador-2]

Hi Igniters,
this is  a great news for the company where I work because they are
Microsoft partners.
We look forward to the news. Let me know if I can contribute to migration.
Thank you

2015-08-18 3:42 GMT+02:00 Nikita Ivanov <[hidden email]>:

> I'm already grinning from ear to ear so release should go as planned :-))
> Awesome news for sure.
>
> As a side historical note: Dmitriy (Setrakyan) and I worked on our 1st
> cross-platform (Java/.NET) in-memory middleware back in 2001-2002. Back
> almost 15 years ago we saw a clear need for Java and MSFT-world to be able
> to work together on in-memory computing middleware. It's immensely
> gratifying that ASF gets a in-memory computing software (as part of Apache
> Ignite) that delivers on that idea.
> --
> Nikita Ivanov
>
>
> On Mon, Aug 17, 2015 at 5:26 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > Hi Igniters,
> >
> > Last week GridGain has agreed to donate its C++ and .NET implementations
> > for Apache Ignite to ASF. This is big news, as now Ignite will be able to
> > add value to C++ and .NET communities. Together with Node.JS client,
> which
> > is under development, this creates a fairly large Ignite ecosystem.
> >
> > These are not basic client APIs, but rather is a full-blown in-memory
> data
> > fabric for .NET and C++ users. The goal is that users of these languages
> > will not have to write any Java code at all in order to use any Apache
> > Ignite features. For example, .NET users will even be able to execute C#
> > closures over Apache Ignite runtime.
> >
> > For the next couple of weeks GridGain will be working on migrating and
> > contributing the code and documentation to Apache Ignite. My hope is that
> > it will get into 1.4 release (assuming that release gods smile upon us).
> >
> > D.
> >
>

--
Gianfranco Murador
Igniter and Software Engineer.

[Alexey Kuznetsov-2]

Just curious: it is possible to use http://www.ikvm.net/ to run Ignite
under .Net
Does anyone investigate IKVM + Ignite?

On Tue, Aug 18, 2015 at 5:16 PM, Gianfranco Murador <[hidden email]>
wrote:

> Hi Igniters,
> this is  a great news for the company where I work because they are
> Microsoft partners.
> We look forward to the news. Let me know if I can contribute to migration.
> Thank you
>
> 2015-08-18 3:42 GMT+02:00 Nikita Ivanov <[hidden email]>:
>
> > I'm already grinning from ear to ear so release should go as planned :-))
> > Awesome news for sure.
> >
> > As a side historical note: Dmitriy (Setrakyan) and I worked on our 1st
> > cross-platform (Java/.NET) in-memory middleware back in 2001-2002. Back
> > almost 15 years ago we saw a clear need for Java and MSFT-world to be
> able
> > to work together on in-memory computing middleware. It's immensely
> > gratifying that ASF gets a in-memory computing software (as part of
> Apache
> > Ignite) that delivers on that idea.
> > --
> > Nikita Ivanov
> >
> >
> > On Mon, Aug 17, 2015 at 5:26 PM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> > > Hi Igniters,
> > >
> > > Last week GridGain has agreed to donate its C++ and .NET
> implementations
> > > for Apache Ignite to ASF. This is big news, as now Ignite will be able
> to
> > > add value to C++ and .NET communities. Together with Node.JS client,
> > which
> > > is under development, this creates a fairly large Ignite ecosystem.
> > >
> > > These are not basic client APIs, but rather is a full-blown in-memory
> > data
> > > fabric for .NET and C++ users. The goal is that users of these
> languages
> > > will not have to write any Java code at all in order to use any Apache
> > > Ignite features. For example, .NET users will even be able to execute
> C#
> > > closures over Apache Ignite runtime.
> > >
> > > For the next couple of weeks GridGain will be working on migrating and
> > > contributing the code and documentation to Apache Ignite. My hope is
> that
> > > it will get into 1.4 release (assuming that release gods smile upon
> us).
> > >
> > > D.
> > >
> >
>
>
>
> --
> Gianfranco Murador
> Igniter and Software Engineer.
>

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[Vladimir Ozerov]

Alexey,
I do not think it makes sense to dig into this at all.

On Tue, Aug 18, 2015 at 1:21 PM, Alexey Kuznetsov <[hidden email]>
wrote:

> Just curious: it is possible to use http://www.ikvm.net/ to run Ignite
> under .Net
> Does anyone investigate IKVM + Ignite?
>
> On Tue, Aug 18, 2015 at 5:16 PM, Gianfranco Murador <[hidden email]>
> wrote:
>
> > Hi Igniters,
> > this is  a great news for the company where I work because they are
> > Microsoft partners.
> > We look forward to the news. Let me know if I can contribute to
> migration.
> > Thank you
> >
> > 2015-08-18 3:42 GMT+02:00 Nikita Ivanov <[hidden email]>:
> >
> > > I'm already grinning from ear to ear so release should go as planned
> :-))
> > > Awesome news for sure.
> > >
> > > As a side historical note: Dmitriy (Setrakyan) and I worked on our 1st
> > > cross-platform (Java/.NET) in-memory middleware back in 2001-2002. Back
> > > almost 15 years ago we saw a clear need for Java and MSFT-world to be
> > able
> > > to work together on in-memory computing middleware. It's immensely
> > > gratifying that ASF gets a in-memory computing software (as part of
> > Apache
> > > Ignite) that delivers on that idea.
> > > --
> > > Nikita Ivanov
> > >
> > >
> > > On Mon, Aug 17, 2015 at 5:26 PM, Dmitriy Setrakyan <
> > [hidden email]>
> > > wrote:
> > >
> > > > Hi Igniters,
> > > >
> > > > Last week GridGain has agreed to donate its C++ and .NET
> > implementations
> > > > for Apache Ignite to ASF. This is big news, as now Ignite will be
> able
> > to
> > > > add value to C++ and .NET communities. Together with Node.JS client,
> > > which
> > > > is under development, this creates a fairly large Ignite ecosystem.
> > > >
> > > > These are not basic client APIs, but rather is a full-blown in-memory
> > > data
> > > > fabric for .NET and C++ users. The goal is that users of these
> > languages
> > > > will not have to write any Java code at all in order to use any
> Apache
> > > > Ignite features. For example, .NET users will even be able to execute
> > C#
> > > > closures over Apache Ignite runtime.
> > > >
> > > > For the next couple of weeks GridGain will be working on migrating
> and
> > > > contributing the code and documentation to Apache Ignite. My hope is
> > that
> > > > it will get into 1.4 release (assuming that release gods smile upon
> > us).
> > > >
> > > > D.
> > > >
> > >
> >
> >
> >
> > --
> > Gianfranco Murador
> > Igniter and Software Engineer.
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[Konstantin Boudnik-2]

Thanks for the contribution! And for the retrospect - very interesting!

Cos

On Mon, Aug 17, 2015 at 06:42PM, Nikita Ivanov wrote:

> I'm already grinning from ear to ear so release should go as planned :-))
> Awesome news for sure.
>
> As a side historical note: Dmitriy (Setrakyan) and I worked on our 1st
> cross-platform (Java/.NET) in-memory middleware back in 2001-2002. Back
> almost 15 years ago we saw a clear need for Java and MSFT-world to be able
> to work together on in-memory computing middleware. It's immensely
> gratifying that ASF gets a in-memory computing software (as part of Apache
> Ignite) that delivers on that idea.
> --
> Nikita Ivanov
>
>
> On Mon, Aug 17, 2015 at 5:26 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > Hi Igniters,
> >
> > Last week GridGain has agreed to donate its C++ and .NET implementations
> > for Apache Ignite to ASF. This is big news, as now Ignite will be able to
> > add value to C++ and .NET communities. Together with Node.JS client, which
> > is under development, this creates a fairly large Ignite ecosystem.
> >
> > These are not basic client APIs, but rather is a full-blown in-memory data
> > fabric for .NET and C++ users. The goal is that users of these languages
> > will not have to write any Java code at all in order to use any Apache
> > Ignite features. For example, .NET users will even be able to execute C#
> > closures over Apache Ignite runtime.
> >
> > For the next couple of weeks GridGain will be working on migrating and
> > contributing the code and documentation to Apache Ignite. My hope is that
> > it will get into 1.4 release (assuming that release gods smile upon us).
> >
> > D.
> >