Skip to main content
Version: 9.x (Current)

The Marketplace

Why always start from scratch​

The Mia-Platform Marketplace contains several code resources to develop your microservices with Mia-Platform.

You can access the Mia-Platform Marketplace from the Design area of Console, when you are creating a new microservice.

You will see a set of Plugins, Examples, Templates and Applications powered and supported by Mia-Platform, you can choose from to easily set-up a single microservice or a bundle of microservices with predefined and tested functionalities.

You can go deeper into the code of templates and examples visiting the Mia-Platform Marketplace Github page.

You can start from a:

  • Plugin: a ready-to-use Microservice.
    Check out the Plugins section for further information.

  • Template: a base repository from which you can start to create a new Microservice.
    Check out the Templates section for further information.

  • Example: a specific use-case, a ready-to-use model to create your microservice.
    Check out the Examples section for further information.

  • Docker Image Name: an existing Docker image of a Microservice.
    Check out the Create services section for further information.

  • Application: a bundle of resources including Plugins, Templates and Examples.

You can search for Microservices, filtering by type: Plugins, Templates, Examples and/or Applications.

Otherwise, you can search for them by category.

The results of your search will appear organized by category.

new-examples

Marketplace component lifecycle​

Each Marketplace component has a predetermined development lifecycle.

lifecycle-stages

These are the expected stages along the component lifecycle:

  • Coming soon: this label aims to inform Marketplace users about the existence of a new component whose implementation has just started (these components are not usable)

  • Preview: first usable release, there may be bugs and they may be subject to undocumented breaking changes

  • Beta: the implementation is completed and there cannot be any undocumented breaking changes however there could still be bugs, hence it must be used carefully

  • Stable: the implementation is stable (bug free). Consequently, this stage represents the component period before its official release documented in the release note