Self-Managed Micro-Integrations

In many cases, external data is not always available in a form that is compatible for an event-driven architecture. Things like databases, filesystems, and SaaS applications need to be event-enabled to integrate with your event-driven architecture and connect to Solace event brokers. For example:

  • A filesystem isn’t event-enabled by default, but it might be useful to have an event each time a file is created in a directory.

  • Database operations are not event-enabled by default, but it might be useful to have an event whenever there’s a Create, Update, or Delete (CRUD) operation performed to a table.

Self-Managed Micro-Integrations provide data integration between third-party services (message brokers, databases, filesystems, cloud services and applications, and so on) with Solace event brokers. They ingest (on-ramp) and egress (off-ramp) data to and from your Solace event brokers to integrate things that are normally not event-enabled to support your event-driven architecture.

Self-Managed Micro-Integrations are standalone and can be deployed independently of other integrations or infrastructure. All Self-Managed Micro-Integrations are built on a common Spring framework. You don't need in-depth knowledge of Spring or Java to use Self-Managed Micro-Integrations.

The Common Framework for Self-Managed Micro-Integrations

Self-Managed Micro-Integrations share these common features and capabilities:

A Common Deployment Model

Each Self-Managed Micro-Integration is available as:

  • an executable package for deployment on compute resources such as bare metal, VMs, and cloud compute services.

  • a pre-built container image suitable for deployment on container runtimes such as Docker, Podman, or orchestration through Kubernetes as examples.

Common Runtime Models

Each Self-Managed Micro-Integration can run:

  • as a single, standalone Micro-Integration.

  • in a failover configuration that provides for an Active instance and 1-n “hot” Standby instances for high-availability.

  • as 2-n instances in Active-Active mode, providing horizontal scaling of Micro-Integrations. In this deployment model, the source data services must be capable of handling multiple consumers, as in non-exclusive or partitioned queues on the Solace event broker.

A Common Configuration Model

Each Self-Managed Micro-Integration:

  • uses Spring Framework technologies and Spring configuration concepts, such as config file formats, names, Spring profiles, property names, and so on.

  • comes with a complete, well-documented sample configuration to allow users to configure the Micro-Integrations without prior knowledge of Java or Spring.

Common HTTP/JMX Endpoints

To access runtime information for Self-Managed Micro-Integrations:

  • use the Spring Actuator project to expose endpoints (which are exposed or hidden is part of the operator's configuration), providing information on the instance such as:

    • Health check

    • Metrics

    • Configuration/environment information (including JVM)

    • Log access

  • provide a common logging framework support:

    • Each Micro-Integration is built using the popular Logback logging framework.

    • Logback provides advanced logging features such as auto rollover by size or date, archiving, log export to common logging services, and log levels.

  • support common, configured metrics export to common monitoring tools:

    Micro-Integrations are integrated with the Micrometer Application Observability project to provide a common, easily configured metrics export to many popular monitoring tools or services such as:

    • AppOptics

    • Azure Monitor

    • Netflix Atlas

    • CloudWatch

    • Datadog

    • Dynatrace

    • Elastic

    • Ganglia

    • Graphite

    • Humio

    • Influx/Telegraf

    • JMX

    • KairosDB

    • New Relic

    • OpenTelemetry Protocol (OTLP)

    • Prometheus

    • SignalFx

    • Google Stackdriver

    • StatsD

    • Wavefront

Running and Managing Self-Managed Micro-Integrations

Solace provides a number of Micro-Integrations.

For information about:

Downloading Self-Managed Micro-Integrations

You can find additional information, including links to download Self-Managed Micro-Integrations, on the Integration Hub.

License

The Self-Managed Micro-Integrations are licensed under the Solace Community License, Version 1.0. For more information, see the LICENSE file in the download package for your Micro-Integration.

Support

Community support (best effort) is offered from Solace Developer Community forums. For premium support options, contact Solace.