https://docs.edgelq.com/build-a-service/concepts/ Recent content in Concepts on SPEKTRA Edge Hugo en https://docs.edgelq.com/build-a-service/concepts/meta/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/meta/ To build a multi-service framework, we first need a special service, that provides service registry offers. Using it, we must be able to discover: List of existing Regions List of existing Services List of existing Resources per Service List of existing regional Deployments per Service. This is provided by the meta.goten.com Service, in the Goten repository, directory meta-service. It follows the typical structure of any service, but has no cmd directory or fixtures, as Goten provides only basic parts. https://docs.edgelq.com/build-a-service/concepts/registry/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/registry/ Meta service provides API allowing inspection global environment, but we also need a side library, called EnvRegistry: It must allow a Deployment to register itself in a Meta service, so others can see it. It must allow the discovery of other services with their deployments and resources. It must provide a way to obtain real-time updates of what is happening in the environment. Those three items above are the responsibilities of EnvRegistry module. https://docs.edgelq.com/build-a-service/concepts/metadata/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/metadata/ As a protocol, Goten needs to have protocol-like properties. One of the thems is the requirement that resource types of all Services managed by Goten must contain metadata objects. It was already mentioned multiple times, but let’s put a link to the Meta object again https://github.com/cloudwan/goten/blob/main/types/meta.proto. Resource type managed by Goten must satisfy interface methods (you can see in the Resource interface defined in the runtime/resource/resource.go file): GetMetadata() *meta.Meta EnsureMetadata() *meta. https://docs.edgelq.com/build-a-service/concepts/store/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/store/ We mentioned MultiRegion policy-holder resources, and their importance when it comes to evaluating region syncing information based on resource name. There is a need to have a MultiRegion PolicyStore object, that for any given resource name returns a managing MultiRegionPolicy object. This object is defined in the Goten repository, file runtime/multi_region/policy_store.go. This file is important for this design and worth remembering. As of now, it returns a nil object for global resources though, the caller should in this case take MultiRegionPolicy from the EnvRegistry component from the relevant Service.