-
Notifications
You must be signed in to change notification settings - Fork 58
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
3 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,5 @@ | ||
# What is Generalized Metadata Service (GMS)? [WIP] | ||
# What is Generalized Metadata Service (GMS)? | ||
|
||
Metadata for entities [onboarded](../how/entity-onboarding.md) to [GMA](gma.md), such as a `dataset` and `user`, is served through microservices known as Generalized Metadata Service (GMS). GMS typically provides a [Rest.li](http://rest.li) API and must access the metadata using GMA [DAOs](../architecture/metadata-serving.md). | ||
|
||
|
||
## Central vs Distributed | ||
Any entity such as `datasets` or `users` which are [onboarded](../how/entity-onboarding.md) to GMA can be designed to be served through a separate microservice. | ||
These microservices are called GMS. Although we've a central GMS ([datahub-gms](../../gms)) which serves all entities, | ||
we could easily have multiple GMS, each has responsible for a specific entity such as `dataset-gms`, `user-gms` etc. | ||
GMA is designed to support a distributed fleet of GMS, each serving a subset of the [GMA graph](graph.md). However, for simplicity we include a cenetralized GMS ([datahub-gms](../../gms)) that serves all entities. |