Maybe you can elaborate more on your use case, because usually it is not a technical decision , but driven by user requirements.
> On 9. Jul 2018, at 10:01, Mahesh Talreja <[email protected]> wrote: > > Hi Team, > I am working on Dot Net project and trying to implement > Ignite.Net. > Being new to the world of ignite, and after having a read above transactions > on ( https://apacheignite-net.readme.io/docs/transactions#atomicity-mode ) > I am a bit confused with ignite transaction atomicity-mode's. > > To give you a bit of background, I am working on a project which is being > developed on microservice design/architecture, having plans to be hosted > using docker containers. So to summarise, I am expecting to have a > multiprocess/ multithreaded environment, wherein there can be multiple > instances of a microservice and each instance of a microservice will go ahead > a create an Ignite Node (Client Mode) and get connected to a cluster of > server nodes. > > I am dealing with simple curd operations. Each user action resulting in only > a single curd operation at a time (Get/Put/Remove/Replace). > > So should I go ahead and use transactions (Pessimistic - Repeatable Read) > even when I have single operations in each transaction as it locks the > respective keys and provides sequential execution and is fully ACID compliant > in case of multiple processes, > > Or should I just go ahead with the Atomic mode which provides atomicity and > consistency but I am not sure about locks and sequential execution in case of > multiple processes? >
