You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Neeraj Vaidya <ne...@yahoo.co.in> on 2017/03/26 13:07:41 UTC
Akka vs Ignite
Dear Experts,
While doing development on my application related to telecom projects, I was wondering if Akka would have any specific advantages/disadvantages in comparison to Ignite.
My application is a realtime telecom transactional application.
I can think of the following major pluses for Ignite :
- Support for SQL on the key value store.
- Proven for distributed data. Whereas Akka distributed data module is still experimental.
Regards,
Neeraj
Sent from my iPhone
Re: Akka vs Ignite
Posted by vkulichenko <va...@gmail.com>.
Aleksey,
I think the difference between the products is more in functionality and
APIs provided to user. As Nikita correctly mentioned, Ignite provides much
higher level abstractions. For sure, Akka architecture can have a lot of
similarities with low-level architecture of certain Ignite components, but
this seems to be out of scope of this discussion.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Akka-vs-Ignite-tp11444p11553.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Akka vs Ignite
Posted by ALEKSEY KUZNETSOV <al...@gmail.com>.
does ignite's low level architecture similar to akka's one ?
пн, 27 Мар 2017 г., 2:27 Neeraj Vaidya <ne...@yahoo.co.in>:
> Thanks Nikita and Denis. That really helps.
>
> Ragards,
> Neeraj
>
> Sent from my iPhone
>
> On 27 Mar 2017, at 08:36, Nikita Ivanov <ni...@gmail.com> wrote:
>
> Neeraj - the best way I always describe Akka vs. Ignite is that Akka is a
> framework that could have been used to develop Ignite... Ignite is much
> more higher level platform: SQL/NoSQL, ACID, compute/data grids, etc.
>
> --
> Nikita Ivanov
>
>
> On Sun, Mar 26, 2017 at 11:59 AM, Neeraj Vaidya <neeraj.vaidya@yahoo.co.in
> > wrote:
>
> Thanks Denis, by "latter" you mean Ignite ?
>
> Regards,
> Neeraj
>
> > On 27 Mar 2017, at 05:12, Denis Magda <dm...@apache.org> wrote:
> >
> > Hello Neeraj,
> >
> > I’m not an expert in Akka but having a brief look at it I should say
> that, in general, it’s a framework for highly-concurrent distributed
> computations and real-time streaming processing. Roughly, it’s a
> combination of a distributed map-reduce functionality and streaming engine
> built around Actor concept.
> >
> > While Ignite is a distributed in-memory data platform with a variety of
> components such as ANSI-99 SQL Grid, transactional and ACID compliant data
> grid, compute and streaming grids modules that resemble Akka functionality
> in some way, and more. The upshot is that Akka is outfitted with a subset
> of capabilities Ignite has and, depending on your project’s current goals
> and its future evolvement, that latter might be more attractive since a lot
> of functionality is provided out-of-the-box in a single platform.
> >
> > —
> > Denis
> >
> >> On Mar 26, 2017, at 6:07 AM, Neeraj Vaidya <ne...@yahoo.co.in>
> wrote:
> >>
> >> Dear Experts,
> >> While doing development on my application related to telecom projects,
> I was wondering if Akka would have any specific advantages/disadvantages in
> comparison to Ignite.
> >> My application is a realtime telecom transactional application.
> >> I can think of the following major pluses for Ignite :
> >> - Support for SQL on the key value store.
> >> - Proven for distributed data. Whereas Akka distributed data module is
> still experimental.
> >>
> >> Regards,
> >> Neeraj
> >>
> >> Sent from my iPhone
> >
>
>
> --
*Best Regards,*
*Kuznetsov Aleksey*
Re: Akka vs Ignite
Posted by Neeraj Vaidya <ne...@yahoo.co.in>.
Thanks Nikita and Denis. That really helps.
Ragards,
Neeraj
Sent from my iPhone
> On 27 Mar 2017, at 08:36, Nikita Ivanov <ni...@gmail.com> wrote:
>
> Neeraj - the best way I always describe Akka vs. Ignite is that Akka is a framework that could have been used to develop Ignite... Ignite is much more higher level platform: SQL/NoSQL, ACID, compute/data grids, etc.
>
> --
> Nikita Ivanov
>
>
>> On Sun, Mar 26, 2017 at 11:59 AM, Neeraj Vaidya <ne...@yahoo.co.in> wrote:
>> Thanks Denis, by "latter" you mean Ignite ?
>>
>> Regards,
>> Neeraj
>>
>> > On 27 Mar 2017, at 05:12, Denis Magda <dm...@apache.org> wrote:
>> >
>> > Hello Neeraj,
>> >
>> > I’m not an expert in Akka but having a brief look at it I should say that, in general, it’s a framework for highly-concurrent distributed computations and real-time streaming processing. Roughly, it’s a combination of a distributed map-reduce functionality and streaming engine built around Actor concept.
>> >
>> > While Ignite is a distributed in-memory data platform with a variety of components such as ANSI-99 SQL Grid, transactional and ACID compliant data grid, compute and streaming grids modules that resemble Akka functionality in some way, and more. The upshot is that Akka is outfitted with a subset of capabilities Ignite has and, depending on your project’s current goals and its future evolvement, that latter might be more attractive since a lot of functionality is provided out-of-the-box in a single platform.
>> >
>> > —
>> > Denis
>> >
>> >> On Mar 26, 2017, at 6:07 AM, Neeraj Vaidya <ne...@yahoo.co.in> wrote:
>> >>
>> >> Dear Experts,
>> >> While doing development on my application related to telecom projects, I was wondering if Akka would have any specific advantages/disadvantages in comparison to Ignite.
>> >> My application is a realtime telecom transactional application.
>> >> I can think of the following major pluses for Ignite :
>> >> - Support for SQL on the key value store.
>> >> - Proven for distributed data. Whereas Akka distributed data module is still experimental.
>> >>
>> >> Regards,
>> >> Neeraj
>> >>
>> >> Sent from my iPhone
>> >
>>
>
Re: Akka vs Ignite
Posted by Nikita Ivanov <ni...@gmail.com>.
Neeraj - the best way I always describe Akka vs. Ignite is that Akka is a
framework that could have been used to develop Ignite... Ignite is much
more higher level platform: SQL/NoSQL, ACID, compute/data grids, etc.
--
Nikita Ivanov
On Sun, Mar 26, 2017 at 11:59 AM, Neeraj Vaidya <ne...@yahoo.co.in>
wrote:
> Thanks Denis, by "latter" you mean Ignite ?
>
> Regards,
> Neeraj
>
> > On 27 Mar 2017, at 05:12, Denis Magda <dm...@apache.org> wrote:
> >
> > Hello Neeraj,
> >
> > I’m not an expert in Akka but having a brief look at it I should say
> that, in general, it’s a framework for highly-concurrent distributed
> computations and real-time streaming processing. Roughly, it’s a
> combination of a distributed map-reduce functionality and streaming engine
> built around Actor concept.
> >
> > While Ignite is a distributed in-memory data platform with a variety of
> components such as ANSI-99 SQL Grid, transactional and ACID compliant data
> grid, compute and streaming grids modules that resemble Akka functionality
> in some way, and more. The upshot is that Akka is outfitted with a subset
> of capabilities Ignite has and, depending on your project’s current goals
> and its future evolvement, that latter might be more attractive since a lot
> of functionality is provided out-of-the-box in a single platform.
> >
> > —
> > Denis
> >
> >> On Mar 26, 2017, at 6:07 AM, Neeraj Vaidya <ne...@yahoo.co.in>
> wrote:
> >>
> >> Dear Experts,
> >> While doing development on my application related to telecom projects,
> I was wondering if Akka would have any specific advantages/disadvantages in
> comparison to Ignite.
> >> My application is a realtime telecom transactional application.
> >> I can think of the following major pluses for Ignite :
> >> - Support for SQL on the key value store.
> >> - Proven for distributed data. Whereas Akka distributed data module is
> still experimental.
> >>
> >> Regards,
> >> Neeraj
> >>
> >> Sent from my iPhone
> >
>
>
Re: Akka vs Ignite
Posted by Denis Magda <dm...@gridgain.com>.
Exactly
On Sunday, March 26, 2017, Neeraj Vaidya <ne...@yahoo.co.in> wrote:
> Thanks Denis, by "latter" you mean Ignite ?
>
> Regards,
> Neeraj
>
> > On 27 Mar 2017, at 05:12, Denis Magda <dmagda@apache.org <javascript:;>>
> wrote:
> >
> > Hello Neeraj,
> >
> > I’m not an expert in Akka but having a brief look at it I should say
> that, in general, it’s a framework for highly-concurrent distributed
> computations and real-time streaming processing. Roughly, it’s a
> combination of a distributed map-reduce functionality and streaming engine
> built around Actor concept.
> >
> > While Ignite is a distributed in-memory data platform with a variety of
> components such as ANSI-99 SQL Grid, transactional and ACID compliant data
> grid, compute and streaming grids modules that resemble Akka functionality
> in some way, and more. The upshot is that Akka is outfitted with a subset
> of capabilities Ignite has and, depending on your project’s current goals
> and its future evolvement, that latter might be more attractive since a lot
> of functionality is provided out-of-the-box in a single platform.
> >
> > —
> > Denis
> >
> >> On Mar 26, 2017, at 6:07 AM, Neeraj Vaidya <neeraj.vaidya@yahoo.co.in
> <javascript:;>> wrote:
> >>
> >> Dear Experts,
> >> While doing development on my application related to telecom projects,
> I was wondering if Akka would have any specific advantages/disadvantages in
> comparison to Ignite.
> >> My application is a realtime telecom transactional application.
> >> I can think of the following major pluses for Ignite :
> >> - Support for SQL on the key value store.
> >> - Proven for distributed data. Whereas Akka distributed data module is
> still experimental.
> >>
> >> Regards,
> >> Neeraj
> >>
> >> Sent from my iPhone
> >
>
>
Re: Akka vs Ignite
Posted by Neeraj Vaidya <ne...@yahoo.co.in>.
Thanks Denis, by "latter" you mean Ignite ?
Regards,
Neeraj
> On 27 Mar 2017, at 05:12, Denis Magda <dm...@apache.org> wrote:
>
> Hello Neeraj,
>
> I’m not an expert in Akka but having a brief look at it I should say that, in general, it’s a framework for highly-concurrent distributed computations and real-time streaming processing. Roughly, it’s a combination of a distributed map-reduce functionality and streaming engine built around Actor concept.
>
> While Ignite is a distributed in-memory data platform with a variety of components such as ANSI-99 SQL Grid, transactional and ACID compliant data grid, compute and streaming grids modules that resemble Akka functionality in some way, and more. The upshot is that Akka is outfitted with a subset of capabilities Ignite has and, depending on your project’s current goals and its future evolvement, that latter might be more attractive since a lot of functionality is provided out-of-the-box in a single platform.
>
> —
> Denis
>
>> On Mar 26, 2017, at 6:07 AM, Neeraj Vaidya <ne...@yahoo.co.in> wrote:
>>
>> Dear Experts,
>> While doing development on my application related to telecom projects, I was wondering if Akka would have any specific advantages/disadvantages in comparison to Ignite.
>> My application is a realtime telecom transactional application.
>> I can think of the following major pluses for Ignite :
>> - Support for SQL on the key value store.
>> - Proven for distributed data. Whereas Akka distributed data module is still experimental.
>>
>> Regards,
>> Neeraj
>>
>> Sent from my iPhone
>
Re: Akka vs Ignite
Posted by Denis Magda <dm...@apache.org>.
Hello Neeraj,
I’m not an expert in Akka but having a brief look at it I should say that, in general, it’s a framework for highly-concurrent distributed computations and real-time streaming processing. Roughly, it’s a combination of a distributed map-reduce functionality and streaming engine built around Actor concept.
While Ignite is a distributed in-memory data platform with a variety of components such as ANSI-99 SQL Grid, transactional and ACID compliant data grid, compute and streaming grids modules that resemble Akka functionality in some way, and more. The upshot is that Akka is outfitted with a subset of capabilities Ignite has and, depending on your project’s current goals and its future evolvement, that latter might be more attractive since a lot of functionality is provided out-of-the-box in a single platform.
—
Denis
> On Mar 26, 2017, at 6:07 AM, Neeraj Vaidya <ne...@yahoo.co.in> wrote:
>
> Dear Experts,
> While doing development on my application related to telecom projects, I was wondering if Akka would have any specific advantages/disadvantages in comparison to Ignite.
> My application is a realtime telecom transactional application.
> I can think of the following major pluses for Ignite :
> - Support for SQL on the key value store.
> - Proven for distributed data. Whereas Akka distributed data module is still experimental.
>
> Regards,
> Neeraj
>
> Sent from my iPhone