According to the ArangoDB documentation, using a cluster configuration both erodes ACID guarantees and impacts the performance of queries / api calls depending on how the database is partitioned (and possibly on replication factor). Need to understand and assess the impact of these factors on the data model and the current foxx service implementation, then develop a strategy / approach to mitigating any negative side effects. This information will then be used to inform the refactoring or redesign of the data model and service layer, if needed.
For now, we are going to continue using arango in single-instance mode (possibly with fail over), so this issue will be deferred until such time that DB scaling becomes necessary.
According to the ArangoDB documentation, using a cluster configuration both erodes ACID guarantees and impacts the performance of queries / api calls depending on how the database is partitioned (and possibly on replication factor). Need to understand and assess the impact of these factors on the data model and the current foxx service implementation, then develop a strategy / approach to mitigating any negative side effects. This information will then be used to inform the refactoring or redesign of the data model and service layer, if needed.