MapR Persistent Application Client Container

MapR Persistent Application Client Containers (PACCs) support containerization of existing and new applications by providing containers with persistent data access from anywhere.

MapR Persistent Application Client Containers

Containers have no scalable, out-of-box way to let applications persist state. All data written by containerized applications is typically lost when there is an application or hardware failure. Most options seeking to address this problem have proven to be inadequate for a variety of reasons. Storing data on local nodes, for example, forces IT departments to track down the data and move files when containers are redeployed. In addition, commercially available NAS/SAN-based solutions are not cost-effective and introduce unnecessary overhead.

With the introduction of MapR Persistent Application Client Containers (PACCs), containerized applications can easily leverage all the MapR platform services (MapR XD, MapR Database, MapR Event Store) as a persistent data store.

Key Features

  • Pre-built, certified container image. A Docker image is provided for connecting to all converged data platform services, including MapR-FS, MapR Database, and MapR Event Store. The image is streamlined to include all the necessary bits - no more, no less - required to leverage MapR as a persistent data store for your containerized applications.
  • Flexibility in Deployment. Application containers that leverage MapR PACCs can be deployed on MapR nodes as well as remote client nodes, including nodes in the cloud.
  • Secure authentication at container level, allowing for secure connections. MapR PACCs allow for authentication at a container level to ensure containerized applications only have access to data for which they are authorized. Communications are encrypted to ensure privacy when accessing data in mapR.
  • Docker image available. A Docker image for the MapR PACC is available on Docker Hub. This image can be used as is after brief configuration of cluster location, ticket location (if using security), etc.
  • Dockerfile available. A Dockerfile is also available on GitHub, allowing you to further customize the image as needed to support your specific application needs.

Use Cases

  • Containerizing an Existing Application. Applications store state in the MapR Converged Data Platform, ensuring resilience and availability across application and infrastructure failures. In this use case:
    • Containers can survive application or hardware failures by accessing persisted data upon restart.
    • Containers can move across nodes or even data centers (including cloud environments), yet still retain access to persisted data.

MapR Persistent Application Client Containers

  • Shared Storage for Applications and Analytics. Here, containerized applications persist data to a secure, shared location (the MapR Data Platform), where other applications can access and make use of it. For instance, containerized operational applications can write data to MapR, where analytical applications leveraging Apache Drill, Spark, etc. can then make use of it.
  • Microservices. Microservice applications leverage the complete suite of reliable, scalable data services that only the MapR Converged Data Platform can provide. By leveraging client pathways to MapR Event Store and MapR Database, for example, microservices can immediately gain advantages including statefulness and efficient inter-microservice communication, as well as the simplified deployment model that containers provide.

MapR Persistent Application Client Containers



Containers for Big Data: How MapR Expands Containers Use to Access Data Directly


Persistent Storage for Docker Containers | Whiteboard Walkthrough


Sample Application

MapR PACC Sample.


Persistence in the Age of Microservices: Introducing MapR Converged Data Platform for Docker.

Getting Started with MapR Client Container:


Container Resource on MapR Community.

Technical Documentation

Get started now: Docker Hub

MapR PACC Documentation