Integration - eXist: A NoSQL Database and Application Development Platform - page 364

zopyx.existdb for Plone by Andreas Jung
Connects to eXist via its REST API. An eXist plug-in for Plone CMS
• PHP
php-eXist-db-Client by CuAnnan
Connects to eXist via its XML-RPC API
PheXist by Oscar Celma
Connects to eXist via its SOAP API. Also available for PHP
• Ruby
eXist API by Jenda Sirl
Connects to eXist via its XML-RPC API
rb_exist by Miquel Sabaté Solà
Connects to eXist via its REST API. It was inspired by pyexist
• Scala
XQuery for Scala by Dino Fancellu
Connects to eXist via its XQJ API
Local APIs
A local API enables you to embed eXist into your own Java application by placing the
eXist libraries and configuration files in the classpath of your application and making
function calls to eXist via one of its local APIs. When eXist is embedded in your
application, both your own application's code and eXist's application code run within
the same JVM process.
While there is nothing to stop you from calling eXist's own classes and functions
directly, this is strongly discouraged and not officially supported by the eXist devel‐
opment team. Rather, you are advised to use one of the two available local APIs,
described in “XML:DB Local API” on page 366 and “Fluent API” on page 369 .
So, which local API should you use? There are a few factors to consider:
• Do you want to be able to switch your application between local and remote
eXist instances? If so, then use the XML:DB API, as it is a single API to learn that
supports either local or remote eXist servers.
• If you will only ever use eXist locally in embedded operations, then the Fluent
API provides a more modern and simpler API for working with eXist.