nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Distributing Nuxeo content accross the globe through angular apps ?

Nicolas_Steinme

Hi,

In my company, we'll use Nuxeo next year for DAM/DMS purposes. We have ~60 subsidiaries accross the world and thus we'll need to replicate our central storage to local one (or reginal one).

Thinking about it, I could indeed deploy Nuxeo Box around the world or deploy some smart reverse proxy but I was thinking about something lighter and nicer :

Building a AngularJS based app, using the Nuxeo AngularJS directives. This would be deployed on local sites. App would be in charge to provide a basic "client" for the central storage. Content will be browsed by requesting the API centrally.
For authentication and permissions checkings, AngularJS app would connect to central server to validate user & rights
If user is granted access to a given content, he can download it. Thus, file is fetched either from central repository or from local server if synchronised

We could also assume the whole CRUD actions are made through the angular app + API + Asynchronous sync for assets.

Is the angularJS/Nuxeo + Rest API mature enough to manage this use cases, starting from a 5.8 basis or not yet ?

Thanks, Nicolas

Find more posts tagged with

Comments

bruce_Grant

I do the exact same thing using GWT + REST API for multiple applications, so I know the Nuxeo/API side is capable enough. I

Nicolas_Steinme

Hi Bruce,

Damien_Metzler

Hello,

Developing an Angular app that browses the content repository is quite straightforward.

But what is exactly you problem ? From what I understand, your fear is about the network latency. Using a Single page application should help about that since, the templates for instance would be downloaded only once. After that, the only call will be about retrieving data that is much better than retrieving a full html page.

Beside that, when you talk about synchronisation, it implies some inconsistencies at some time : file present on a server but not replicated on another one. So my question is much about : are you sure the network is a real bottleneck for you app ? And if so, perhaps just a caching proxy on you local sites may suits your needs.

Nicolas_Steinme

Hello Damien,

bruce_Grant

Hi Nicolas,

Nicolas_Steinme

Hi Bruce,