Link Search Menu Expand Document


Micro is a distributed systems runtime environment for the cloud and beyond. You can otherwise think of it as a cloud native development platform. Micro addresses the key requirements for building distributed systems. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks of a platform. Micro deals with the complexity of distributed systems and provides simpler programmable abstractions to build on.

Below is an overview of how Micro is constructed.

Micro focuses on the concept of Development Runtime Infrastructure, creating separation between the varying concerns of development and infrastructure using a runtime as an abstraction layer, then providing entry points for external systems to access services run with Micro.


The runtime is composed of the following features:

  • Clients - Clients act as external entrypoints into the system
  • Services - Core services abstract away the underlying infrastructure


Clients are entrypoints into the system. They enable access to your services through well known entrypoints.

  • api: An api gateway which acts as a single entry point for the frontend with dynamic request routing using service discovery.

  • bot: A slack bot which enables you to query and interact with Micro directly from within slack. It’s great for ChatOps.

  • cli: Access services via the terminal. Every good developer tool needs a CLI as a defacto standard for operating a system.

  • proxy: An identity away proxy which allows you to access remote environments without painful configuration or vpn.

  • web: A dashboard to explore services, describe their endpoints, the request and response formats and query them directly.


Services are the core services that makeup the runtime. They provide a programmable abstraction layer for distributed systems infrastructure.

  • auth: Authentication and authorization is a core requirement for any production ready platform. Micro builds in an auth service for managing service to service and user to service authentication.

  • broker: A message broker allowing for async messaging. Microservices are event driven architectures and should provide messaging as a first class citizen. Notify other services of events without needing to worry about a response.

  • config: Manage dynamic config in a centralised location for your services to access. Has the ability to load config from multiple sources and enables you to update config without needing to restart services.

  • debug: Built in aggregation of stats, logs and tracing info for debugging. The debug service scrapes all services for their info to help understand the overall scope of the system from one location.

  • network: A drop in service to service networking solution. Offload service discovery, load balancing and fault tolerance to the network. The micro network dynamically builds a latency based routing table based on the local registry. It includes support for multi-cloud networking.

  • registry: The registry provides service discovery to locate other services, store feature rich metadata and endpoint information. It’s a service explorer which lets you centrally and dynamically store this info at runtime.

  • runtime: A service runtime which manages the lifecycle of your service, from source to running. The runtime service can run natively locally or on kubernetes, providing a seamless abstraction across both.

  • store: State is a fundamental requirement of any system. We provide a key-value store to provide simple storage of state which can be shared between services or offload long term to keep microservices stateless and horizontally scalable.

Copyright © 2020 Micro Services, Inc.