I'm currently evaluating OrientDB for a new project and I must state that I'm quite impressed :-) Especially the simplicity and performance are great!
One of my concerns is about transactions.
At first, there's a lack of JTA support, which I could either overcome or implement myself with some support of you guys.
Secondly, at least atm there's no support for transactions in a distributed environment, which limits scalability to vertical, if the application needs consistency at any time.
Now my question is about whether or not distributed transactions will be supported in one of the upcoming releases?
unfortunately the JTA support is at low priority because we've received few requests about this. The distributed transaction will be considered after 2.0, so it could be available not before the next 6 months.
Thanks for the quick response. That was really fast :-)
OK, we discussed already about the JTA stuff and I think I could cope with it or implement something by myself.
Distributed transactions is much more crucial from my point of view.
So do I get you right? This feature will be available, but it is just a matter of time?
We need it for sure because we already provide Tx and distributed tx are the next step.
That sounds good! I think it is crucial to have distributed tx ...
+1. I could use JCA/JTA/XA/distributed transactions, too. For JCA, looks like https://github.com/kirpi4ik/orientdb-jca could be a good starting point.
Depends on #1580
We already implemented this. Closing...