MARKLOGIC SERVER

MODULES AND DEPLOYMENT
XQuery, XSLT, and JavaScript code files can reside either on the filesystem or inside
a database. Putting code on a filesystem has the advantage of simplicity. You just place
the code (as .xqy or .sjs scripts, or .xslt templates) under a filesystem directory and
you're done. Putting code in a database, on the other hand, gives you some deployment
conveniences. In a clustered environment, it's easier to make sure that every E-node is
using the same codebase, because each file exists just once in the database and doesn't
have to be replicated across E-nodes or hosted on a network filesystem. You also have
the ability to roll out a big multi-file change as an atomic update. With a filesystem
deployment, some requests might see the code update in a half-written state. Also, with
a database, you can use MarkLogic's security rules to determine who can make updates,
and you can expose (via WebDAV) remote secure access without a shell account.
There's never a need for the programmer to explicitly compile XQuery, XSLT, or
JavaScript code. MarkLogic does, however, maintain a "module cache" to optimize
repeated execution of the same code.
OUTPUT OPTIONS
With MarkLogic, you can generate output in many different formats:
• XML, of course. You can output one node or a series of nodes.
• JSON, the JavaScript Object Notation format common in Ajax applications. It's
easy to translate between XML and JSON. MarkLogic includes built-in translators.
• HTML. You can output HTML as the XML-centric XHTML or as
traditional HTML.
• RSS and Atom. They're just XML formats.
• PDF. There's an XML format named XSL-FO designed for generating PDFs.
• Microsoft Office. Office files use XML as a native format beginning with Microsoft
Office 2007. You can read and write the XML files directly, but to make the
complex formats more approachable, we recommend you use MarkLogic's
Office Toolkits.
• Adobe InDesign and QuarkXPress. Like Microsoft Office, these publishing formats
use native XML formats.
59