For high volume transactions, I'd agree it definitely becomes more of an issue. Also, it's definitely less critical for a chat system, though my usage case (for certain classes) is better compared to what Apache Kafka would be used for (though I believe orientdb should be able to handle this pretty well also), where I want to be sure of the read/write availability of the data so that any node that needs to access it can do so in the exact order, and from the last position they processed (versus a straight queue, where once you pull the data it's gone, and if the client crashed for some reason, the events may be lost).
I used the chat example because I figured it would be more easily understandable, especially as there was already an example of it in the docs that didn't cover a distributed setup. -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
