Feature

Developers already get significant agility with MarkLogic, which provides a fast and iterative way to integrate, store, manage, and search data. By combining MarkLogic and containers, developers can release code even faster.

MarkLogic supports containers for development and production purposes so you can develop and collaborate with greater ease and speed. If, for instance, you use MarkLogic + Docker to pack, ship, and run applications within containers, developers simply write an application, place it in a container, and deploy.

What’s the Difference between Virtual Machines and Containers?

Deploying MarkLogic in virtual machines (VMs) enables true network separation: VMs have a full operating system (OS) with its own memory management installed, and resources are shared for the guest OS and hypervisor. This makes it possible to run many instances of one or more operating systems, in parallel, on a single machine or host.

In comparison, you can run simultaneous containers on a single OS without needing a resource-heavy hypervisor. You can run more containers on a given hardware combination than if you were using virtual machines. This makes containers a lightweight, shared-resource, cost-effective alternative to VMs.

VMs should be used if you need to run multiple applications on multiple servers, but containers are a good alternative if you need to run many copies of a single application.

If you’d like to learn more about Containers in MarkLogic, explore the technical resources below.