# Introduction

The standalone runner is the vanilla runner, totally clean, with no framework. It's mainly used when no framework is configured, although it can be used with any framework, it just doesn't take advantage of the features it provides. The difference from other runners that are built to take the most of the underlying framework, it requires more involvement from the user.

For example, while most of frameworks provides an event mechanism out of the box, in this case the user needs to provide the listener manually, as well as inject the dependencies, as no application context is setup. As the reader can guess, this runner only allows the traditional approach.

Currently it only supports the builder approach, with the setter methods. However we are working on providing an option to use a properties file. It would still use the builder, but instead with setter methods, passing a configuration file.

# Get started

Following the get started section, this covers steps 2 and 7.

# Add the maven dependency for the runner (step 2)


# Build the runner (step 7)

Like the rest of the runners, the standalone runner is built from a builder. Each runner provides a class with an static method builder().

Bear in mind that there are two mandatory parameters for all kind of runner: the driver and at least one migration package or class.


# Configuration

Visit the configuration section in the runner page to see the list of the basic runner's properties.

# Features

# Dependency injection

This feature allows you to inject your own dependencies to your migration classes in the methods directly or at constructor level. Mongock is intelligent enough to handle it. However you need to somehow provide these dependencies. The standalone builder provides the following methods:

The example section shows how to use it in the builder.

# Events

As explained in the events page, Mongock provides three Events: StartedEvent, SuccessEvent and FailureEvent. In the standalone context are represented by:

As there is no framwework managing the dependencies, we need to manually inject the listner for each event type, which are basically Java consumers.

import io.mongock.runner.core.event.MigrationFailureEvent;
import io.mongock.runner.core.event.MigrationStartedEvent;
import io.mongock.runner.core.event.MigrationSuccessEvent;
public class MongockEventListener {
public static void onStart(MigrationStartedEvent event) {
System.out.println("[EVENT LISTENER] - Mongock STARTED successfully");
public static void onSuccess(MigrationSuccessEvent event) {
System.out.println("[EVENT LISTENER] - Mongock finished successfully");
public static void onFail(MigrationFailureEvent event) {
System.out.println("[EVENT LISTENER] - Mongock finished with failures: "
+ event.getMigrationResult().getException().getMessage());

The example section shows how to use it in the builder.

# Example

MongockRunner MongockRunner = MongockStandalone.builder()
//mandatory methods
.setDriver(MongoSync4Driver.withDefaultLock(mongoClient, MONGODB_DB_NAME))
//optional methods
.addDependency("my-bean", myBean)
new HashMap())
.setLegacyMigration(new MongockLegacyMigration(
.setTrackIgnored(false)//default false
.setEnabled(true)//default true
.dontFailIfCannotAcquireLock()//by default, it does throw a MongockException