cancel
Showing results for 
Search instead for 
Did you mean: 

Is better to have two repositories on one Nuxeo instance or to have two Nuxeo instances? Why?

Daniel_Téllez
Champ in-the-making
Champ in-the-making

Having in mind that two repositories in one Nuxeo instance (AFAIK) don't have benefits such as transactions between repos, at least at web level, is it not better to deploy two (or more) Nuxeo instances and implement simple actions to do transfers between them using REST ?

1 ACCEPTED ANSWER

Alain_ESCAFFRE
Star Contributor
Star Contributor

Repositories strategy really depends on use cases:

  • some projects uses several repositories for one application so as to do data partitioning. The main consequence is that you have to deal with a federated search on your repositories, in your app directly.
  • you can do REST communications between two instances. There is no doubt that such REST exchanges (Automation based) between Nuxeo instances will appear in the Nuxeo roadmap, as supplemental plugins, either from Nuxeo or from the community. Note that it is already possible to do remote publishing between two Nuxeo instances through REST (although this doesn't use Automation, as it predates it).

View answer in original post

2 REPLIES 2

Alain_ESCAFFRE
Star Contributor
Star Contributor

Repositories strategy really depends on use cases:

  • some projects uses several repositories for one application so as to do data partitioning. The main consequence is that you have to deal with a federated search on your repositories, in your app directly.
  • you can do REST communications between two instances. There is no doubt that such REST exchanges (Automation based) between Nuxeo instances will appear in the Nuxeo roadmap, as supplemental plugins, either from Nuxeo or from the community. Note that it is already possible to do remote publishing between two Nuxeo instances through REST (although this doesn't use Automation, as it predates it).

Any documentation on this remote publishing through REST?