Re: Ignite 2.10. Performance tests in Azure

[jjimeno <jj...@omp.com>]

It's strange, as that's not what is stated in the documentation:

https://ignite.apache.org/docs/latest/key-value-api/basic-cache-operations#atomic-operations
<https://ignite.apache.org/docs/latest/key-value-api/basic-cache-operations#atomic-operations>  

otherwise, why would we need specific transactional caches?

Regarding collocated computing:  We have to work in C++ and, since Ignite
nodes use Java, I don't see how it is possible to send a C++ piece of code
(like a lambda) so that it gets executed within the node... 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.10. Performance tests in Azure

[Stephen Darlington <st...@gridgain.com>]

> otherwise, why would we need specific transactional caches?

Transactional caches rollback the update in the event of failure; atomic caches do not.

> Regarding collocated computing:  We have to work in C++ and, since Ignite
> nodes use Java, I don't see how it is possible to send a C++ piece of code
> (like a lambda) so that it gets executed within the node... 

With C++ you’d need to deploy the code in advance.

You’re talking about peer-class loading, but that’s not a necessary part of colocated computing.

Regards,
Stephen