Edit on Github
Open
Microservice
Guide
The open standard for reusable microservices

Why OMG?

Microservices, by design, are intended to be highly reusable, operational-specific and language-agnostic. This guide defines the standard that defines how to interface with microservices to provide a blueprint for consistency and reusability. By following this documentation, developers will be able to create a platform that is well-documented and portable while not compromising flexibility.

The old way of communicating software architecture and design through whiteboards and diagrams is immediately out of date and often becomes difficult to read and understand. By mapping your microservice architecture using pre-defined yaml by OMG, developers are given a way to describe architecture and operational requirements as human-readable structured data.

Having these models in plain text files gives developers a framework to effectively communicate architecture, service to service communication, and operational complexities to many different audiences.

Reusability

Focus is stressed on services being highly reusable between applications and platforms.

Management

Define how to interface with the service, lifecycle management, scaling, among other requirements.

Documentation

Services inherit documentation through a well defined configuration of commands, arguments and output.

OMG Supporters

Here are some of the top companies that uphold the OMG standard:

Asyncy

Asyncy

Build smarter applications

Visit Site →
Storyscript

Storyscript

A Goal-oriented Cloud Native Programming Language that choreographs microservices.

Visit Site →
Contact

Your company

Open a PR or contact us if you'd like to be featured here.

Contact