Self-Managed Micro-Integrations

Databases, filesystems, and SaaS applications aren't event-enabled by default, but your event-driven architecture needs them to participate in it. Self-managed Micro-Integrations solve this by providing standalone data integration between these third-party systems and Solace event brokers, ingesting (on-ramp) and egressing (off-ramp) data between them. Self-managed Micro-Integrations are built on a common Spring framework, though you don't need Spring or Java knowledge to use one.

Understanding Self-Managed Micro-Integrations

For a deeper look at how self-managed Micro-Integrations are structured and how data flows through them, see Self-Managed Micro-Integration Architecture.

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.

For more information, see Resource Requirements for Self-Managed Micro-Integrations , Deploying Your Self-Managed Micro-Integration , and Modifying the Container Configuration.

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.

For more information, see Redundancy Configuration .

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.

For more information, see Understanding the application.yml File and Spring Profiles and Property File Locations.

Common HTTP/JMX Endpoints

Each Micro-Integration provides common HTTP/JMX endpoints for accessing runtime information:

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

    • Health check

    • Metrics

    • Configuration/environment information (including JVM)

    • Log access

  • providing 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.

  • supporting 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 Azure Monitor, Netflix Atlas, Datadog, Dynatrace, Prometheus, and more. For the full list, see the Micrometer documentation.

For more information, see Step 7: Configuring and Using the Health Endpoint, Managing Metrics, and Adding a Monitoring System.

Ready to see this in action? Try Try a Micro-Integration, an end-to-end tutorial that walks you through configuring, deploying, and verifying a Micro-Integration using the Message Transform connector as a worked example.

Running and Managing Self-Managed 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.

For information about the features and fixes included in a specific version of a Micro-Integration, log in to products.solace.com and look for the HTML release notes located in the same download folder as your Micro-Integration.

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.