Microservices Engine
Managed Nacos, ZooKeeper or Eureka registry and configuration centre, plus a cloud-native gateway.
- Provider
- alibabacloud
- Category
- Operations
- Official docs
- https://www.alibabacloud.com/help/en/mse
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| consensus | enum | none | raft | paxos | zab | no | none | inherited |
| engine | enum | nacos | zookeeper | eureka | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| nodes | integer | — | no | — | inherited |
| replicated | boolean | — | no | false | ▸ true |
| role | enum | metadata | lock | discovery | placement | sharding | leader-election | config | yes | — | ▸ discovery |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
shared-dependency-without-redundancy
The design requires redundant discovery, but this DNS or coordination service, which everything depends on, runs on a single provider or a single replica. Its failure is the whole system's failure.
- — all of these hold:
- — the design requirement `availability.discoveryRedundant` is true
- — any of these hold:
- — the node's `redundantProviders` is false
- — the node's `replicated` is false
stateful-engine-pinned-to-single-zone
A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.
- — all of these hold:
- — the node sits inside exactly 1 availability-zone group
- — any of these hold:
- — the node's `failover` is "none"
- — the node's `replicated` is false
- — the node's `replication` is "none"
nodes:
- { id: "mse", component: "alibaba-mse" }AWS Cloud Mapaws-cloud-mapAzure Arcazure-arcAzure Device Registryazure-device-registryDurable Objectscloudflare-durable-objectsApache Helixapache-helixConsulconsulGeneric coordination servicecoordination-serviceetcdetcdEurekaeurekaNacosnacosOxiaoxiaApache ZooKeeperzookeeperService Directorygoogle-service-directoryEndpointsk8s-endpointsOpenStack Blazaropenstack-blazarOpenStack Cyborgopenstack-cyborgOpenStack Placementopenstack-placement
# yaml-language-server: $schema=../../schema/component.schema.json # Microservices Engine (MSE): managed registry and configuration centre instances running Nacos, # ZooKeeper or Eureka, plus a cloud-native gateway ("What is MSE"). A registry instance is a # replicated cluster; the consensus protocol follows the engine that is chosen. schemaVersion: "1" type: "component" id: "alibaba-mse" kind: "coordination-service" provider: "alibabacloud" docs: "https://www.alibabacloud.com/help/en/mse" defaults: managed: true role: "discovery" replicated: true properties: engine: type: "enum" values: ["nacos", "zookeeper", "eureka"]