Product & Development
One of the main assets of the Nuxeo Platform is the richness of its APIs: CMIS, REST, WebServices, WSS, Content Automation. Content Automation is a subset of our REST API and is probably the most powerful and simplest means to access Nuxeo. Its strength and richness lies in its ability to provide access to all the services offered within the Nuxeo Platform, but also because of how it integrates with other Nuxeo tools, such as Nuxeo Studio for customizing it, or Nuxeo IDE for extending.
From our wiki:Content Automation is a Nuxeo service that exposes commons actions you do on a Nuxeo application as atomic operations so that one can assemble them to create complex business rules and logic, without writing any Java code.
In other words, content automation provides a high level API over Nuxeo services – an API made up of operations that can be assembled into
During the development of Nuxeo Platform 5.5 (on the 5.4.3-SNAPSHOT branch) Nuxeo has moved the application to a fully POJO (Plain Old Java Objects, if you wonder what it means) based distribution. This decision was motivated by our desire to abandon the RMI exposition primarily because RMI/EJBs introduces complexity along with poor performance, plus we prefer the REST exposition of our API.
Now that this modification has been completed, we were curious about what this new 5.4.3-SNAPSHOT distribution without EJB would bring us in terms of performance against our old distribution with EJBs.
Here is the result: