Continuous Integration Status

Branch GCC 5.5 and 7.5.0 Visual Studio 2015  
Xcode 12.4 Visual Studio 2017  
Clang 9.0 Visual Studio 2019  
master Linux Build Status Windows Build status Code Coverage Status
development BuildAndTestNix BuildAndTestWindows Windows Build status (development) Code Coverage Status (development)

Coverity Scan Build Status

C++ Micro Services

Documentation Status (stable) Documentation Status (development)



The C++ Micro Services project is a collection of components for building modular and dynamic service-oriented applications. It is based on OSGi, but tailored to support native cross-platform solutions.

Proper usage of C++ Micro Services patterns and concepts leads to systems with one or more of the following properties:

  • Re-use of software components
  • Loose coupling between service providers and consumers
  • Separation of concerns, based on a service-oriented design
  • Clean APIs based on service interfaces
  • Extensible and reconfigurable systems


None, except a recent enough C++ compiler. All third-party library dependencies are included and mostly used for implementation details.

Supported Platforms

The library makes use of C++14 language and library features and compiles on many different platforms.

Recommended minimum required compiler versions:

  • GCC 5.5
  • Clang 9.0
  • Clang from Xcode 12.0
  • Visual Studio 2015

You may use older compilers, but certain functionality may not be available. Check the warnings printed during configuration of your build tree. The following are the absolute minimum requirements:

  • GCC 5.1
  • Clang 9.0
  • Clang from Xcode 12.0
  • Visual Studio 2015 (MSVC++ 14.0)

Recommended minimum required CMake version:

  • CMake 3.12.4

For all CI builds through GitHub Actions, the CMake version (and version of other provided software) we use is determined by the software provided on the GitHub-hosted runners.

For information about the specific versions of software the runners use, please see the following resources:

  • ubuntu-18.04 Runner Information <>
  • macos-10.15 Runner Information <>
  • windows-2016 Runner Information <>
  • windows-2019 Runner Information <>

Below is a list of tested compiler/OS combinations:

  • GCC 5.5 (Ubuntu 18.04) via GitHub Actions
  • GCC 7.5.0 (Ubuntu 18.04) via GitHub Actions
  • Clang 9.0 (Ubuntu 18.04) via GitHub Actions
  • Apple Clang, Xcode 12.0.1 (OS X 10.15.7) via GitHub Actions
  • Visual Studio 2015 via Appveyor
  • Visual Studio 2017 via GitHub Actions
  • Visual Studio 2019 via GitHub Actions
  • MinGW-w64 via GitHub Actions

Code of Conduct welcomes developers with different backgrounds and a broad range of experience. A diverse and inclusive community will create more great ideas, provide more unique perspectives, and produce more outstanding code. Our aim is to make the CppMicroServices community welcoming to everyone.

To provide clarity of what is expected of our members, CppMicroServices has adopted the code of conduct defined by This document is used across many open source communities, and we believe it articulates our values well.

Please refer to the Code of Conduct for further details.

Quick Start

Start by cloning the project repository. It is important to note that since the project utilizes git submodules, you must clone the repository with the –recursive flag. This will also clone the submodules and place them in their respective directories. For further reading about how git submodules work and how to clone them into an already existing repository on your disk, please see Git’s documentation.

Essentially, the C++ Micro Services library provides you with a powerful dynamic service registry on top of a managed lifecycle. The framework manages, among other things, logical units of modularity called bundles that are contained in shared or static libraries. Each bundle within a library has an associated cppmicroservices::BundleContext object, through which the service registry is accessed.

To query the registry for a service object implementing one or more specific interfaces, the code would look like this:

#include "cppmicroservices/BundleContext.h"
#include "SomeInterface.h"

using namespace cppmicroservices;

void UseService(BundleContext context)
  auto serviceRef = context.GetServiceReference<SomeInterface>();
  if (serviceRef)
    auto service = context.GetService(serviceRef);
    if (service) { /* do something */ }

Registering a service object against a certain interface looks like this:

#include "cppmicroservices/BundleContext.h"
#include "SomeInterface.h"

using namespace cppmicroservices;

void RegisterSomeService(BundleContext context, const std::shared_ptr<SomeInterface>& service)

The OSGi service model additionally allows to annotate services with properties and using these properties during service look-ups. It also allows to track the life-cycle of service objects. Please see the Documentation for more examples and tutorials and the API reference. There is also a blog post about OSGi Lite for C++.

Git Branch Conventions

The Git repository contains two eternal branches, master and development. The master branch contains production quality code and its HEAD points to the latest released version. The development branch is the default branch and contains the current state of development. Pull requests by default target the development branch. See the CONTRIBUTING file for details about the contribution process.