dice.yml

The platform describes the overall environment in which the microservice runs by declaration of developers, and transforms the declaration into the process of environment building.

The declaration of the YAML file can be divided into the following two parts:

• Microservice declaration, including the number of microservices, as well as the resources required by each microservice, the number of replicas, ports, environment variables, and even the domain name of the external gateway and the forwarding settings of the gateway.
• Extended service settings, namely addon. Developers only need to declare the addon involved in the application, such as MySQL, and specify its specification and version, then the platform will automatically create MySQL for the application and pass the configuration to the microservice by environment variables. Meanwhile, the addon is scalable, so you can integrate almost all addons into the platform.

You may question that K8s YAML is also declarative, but why not use K8s YAML? K8s itself is not a developer-oriented platform, but platform-oriented. There are too many infrastructure details in K8s YAML that developers do not care.

By dice.yml, develops can run the deployment process verified on the central platform in the environment of customer without modification.