NATS uses cookies to ensure you get the best experience on our website. Continuing to use this site assumes compliance with our Privacy Policy.

NATS is outstanding at moving data between endpoints - but what kinds of endpoints? You may have legacy applications that use some proprietary data sources, or perhaps you are migrating from another messaging technology onto NATS. For cases like these, you’ll want to take advantage of the NATS Connector Framework.

The NATS Connector Framework

The NATS Connector Framework provides a foundation to build a connector - an application that moves data into and out of NATS. In creating the connector framework, NATS tenets of simplicity, usability, and community were kept in mind. This resulted in a simple, extensible, and single purposed framework for users to quickly and easily build reusable bridges between NATS and other technologies.


The NATS Connector framework is written in Java - Java is popular, known by developers, and most technologies - especially legacy - provide a Java API. This will allow the connector framework to be used in bridging a multitude of different technologies.

For extensibility, the connector framework was designed with a plug-in architecture. Developers code a class to a simple, straightforward java interface, then a connector instance is started referencing their class. That’s it - the framework does the rest - logging, startup and shutdown, event management, and basic setup and usage of NATS. While NATS is already simple and easy to use, this allows valuable time to be focused on domain expertise rather than writing general application code for a bridge.


With the plugin architecture of the ready-to-use framework, creating connectors is straightforward. We on the NATS team would love to see community users develop and share connectors. We’ll gladly link to user contributions, and include these in the growing list of community developed NATS projects here.

As the NATS Connector framework is open source, don’t forget that you have a say. Contact the NATS team with ideas, suggestions, or comments, and feel free to go ahead and submit pull requests. Let us know of the connectors you build! To coin a phrase, “All of us are smarter than any of us”.


For this tutorial, I’ll be using IntelliJ IDEA as an IDE to setup the project and generate code. In the interest of brevity, I’ll build a simple “file” connector - writing incoming NATS messages to a file, and when a particular file is present, publishing a NATS message with the file contents.

The tutorial includes…

Project Creation

We’ll create a project from scratch using the OSS coordinates to download the NATS Connector Framework. Note, there are other options such as downloading the github repository and building the framework yourself using maven.

Implementation of Connector Interfaces

The tutorial demonstrates implementing connector interfaces to build a plug-in. The interface documentation can be found here.

I’ll implement the interfaces required for a NATS connector framework, and provide required code to create a stand-alone application utilizing the framework.

Running a Connector

This will show the new connector in action, generating and publishing NATS messages from file contents and creating files from incoming NATS messages.

It takes just minutes to create a connector so the tutorial is short:

What’s Next?

The future is wide open, and we’re planning on creating a number of connectors including RabbitMQ and Apache Kafka to name a few - if there is one you’d like to see or contribute, don’t hesitate contact us or open an issue. Visit our Community Page!

If you’d like to look at a full featured connector, check out the NATS Redis Publish/Subscribe Connector.

Tutorial Code

Below is the entirety of java code created for this tutorial:

import io.nats.client.ConnectionFactory;
import io.nats.client.Message;
import io.nats.connector.Connector;
import io.nats.connector.plugin.NATSConnector;
import io.nats.connector.plugin.NATSConnectorPlugin;
import io.nats.connector.plugin.NATSEvent;
import org.slf4j.Logger;

import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
import java.util.concurrent.Executors;

public class FileConnector implements NATSConnectorPlugin
    Logger logger = null;
    NATSConnector connector = null;
    FileDataStore fileDataStore = null;

     * Simulate a data source/sink, by reading and writing
     * files to /tmp
    public class FileDataStore implements Runnable

        static final String SOURCE_FILE = "/tmp/demo_import";
        static final String DEST_FILE   = "/tmp/demo_export";

        // use a volatile for brevity here in non critical code.
        volatile boolean finished = false;

        int fileCount = 0;

        public FileDataStore() {

        public void run() {
            Message m = new Message();
            Path p = Paths.get(SOURCE_FILE);

            while (!finished) {
                try {

                    m.setData(new String(Files.readAllBytes(p)).getBytes());

                    // delete the file we just sent

                } catch ( ioe) {
                    logger.debug("Unable to read send file.");
                } catch (Exception e) {

        public void finish() {
            finished = true;

        public void write(byte[] data) {

            // write data to a new file.
            String fileName = DEST_FILE + "_" + fileCount++;

            try {
                File f = new File(fileName);
                BufferedWriter bw = new BufferedWriter(new FileWriter(f));
                bw.write(new String(data));
            catch (Exception e) {

    public boolean onStartup(Logger logger, ConnectionFactory connectionFactory) {
        this.logger = logger;
        return true;

    public boolean onNatsInitialized(NATSConnector natsConnector) {
        try {
            connector = natsConnector;

            // start our
            fileDataStore = new FileDataStore();

        } catch (Exception e) {
            return false;
        return true;

    public void onNATSMessage(Message message) {

    public void onNATSEvent(NATSEvent natsEvent, String s) {;

    public void onShutdown() {
        if (fileDataStore != null)

    public static void main(String[] args)
        System.setProperty(Connector.PLUGIN_CLASS, FileConnector.class.getName());

        try {
            new Connector(null).run();
        } catch (Exception e) {


Back to Blog