Hi Thanks for your response. Actually I'm working on a C++ project where multiple C++ processes run in parallel. Each process should connect to Ignite Server initially and start a transaction. Cassandra is used as persistent store(The main reason to use ignite on top of Cassandra is for the purpose of transactions, since Cassandra does not support transactions).Then data will be extracted by the process from the server, process the data, update/delete/insert data into Ignite server and later some more data might be required to be extracted and processed or data might be updated/deleted/insert randomly depending upon the data that is received/extracted by the process. In between the transaction might be required to be rolled back depending upon business logic or errors/exceptions. Finally the transaction is commited if everything went fine with in a process. Then it can start another transaction. So I'm looking for a way to perform the operations on Ignite from my C++ process.
Number of processes running in parallel can be around 150-200 max. The data processed by each process is not very large. It can be at max 50-70 Mb per transaction. I need to use a separate transaction context on each process. So I need to use a separate C++ Ignite client with additional logic of converting queries to get,put operations and perform transactions. But Ignite C++ is not light weight hence starting a separate Ignite C++ instance for each of my C++ process might have impact on memory and performance. But If ODBC supported transactions it would not have much impact, since ODBC is a light weight client. I want to use Ignite server just like a RDBMS server and connect to it using thin client. can u suggest any solution -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
