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.

Foundation versus WebServices API?

kapil_k

Where can I find some comparison between the features and capabilities of Foundation versus WebServices API ?
Since the Foundation API works in embedded mode - what are the implications on Scalability? Is the embedded topology scalable with a cluster?

Thanks,
Kapil

Find more posts tagged with

Comments

pmonks

The Web Services API is implemented as a layer on top of the Foundation Services API, so it doesn't really make sense to compare them directly.

It's best to think of the Foundation Services API as being Alfresco - everything else (Web Services, Web Scripts, JCR, Javascript API, PHP API, WebDAV, CIFS, FTP, NFS, Web Client UI, etc. etc.) are simply layers on top of "native Alfresco" (the Foundation Services API). Capabilities such as clustering are built into the repository (ie. into the Foundation Services API), so it doesn't really matter which access mechanism you use - they all behave much the same when it comes to this (and other) capabilities.

What's more relevant is how you wish your users and/or other systems to access Alfresco - that's the single biggest factor in determining which of the various access mechanisms is most appropriate.

Cheers,
Peter