https://docs.edgelq.com/build-a-service/concepts/organization/ Recent content in Goten organization on SPEKTRA Edge Hugo en https://docs.edgelq.com/build-a-service/concepts/organization/server/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/organization/server/ The server should more or less be already known from the developer guide. We will provide some missing bits here only. When we talk about servers, we can distinguish: gRPC Server instance that is listening on a TCP port. Server handler sets that implement some Service GRPC interface. The following code snippet from IAM shows this: grpcServer := grpcserver.NewGrpcServer( authenticator.AuthFunc(), commonCfg.GetGrpcServer(), log, ) v1LimMixinServer := v1limmixinserver.NewLimitsMixinServer( commonCfg, limMixinStore, authInfoProvider, envRegistry, policyStore, ) v1alpha2LimMixinServer := v1alpha2limmixinserver. https://docs.edgelq.com/build-a-service/concepts/organization/controller/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/organization/controller/ You should know about controller design from the developer guide. Here we give a small recap of the controller with tips about code paths. The controller framework is part of the wider Goten framework. It has annotations + compiler parts, in: https://github.com/cloudwan/goten/blob/main/annotations/controller.proto https://github.com/cloudwan/goten/tree/main/compiler/controller You can read more about the Goten compiler. For now, in this place, we will talk just about generated controllers. There are some runtime elements for all controller components (NodeManager, Node, Processor, Syncer…) in runtime/controller direction in Goten repo: https://github. https://docs.edgelq.com/build-a-service/concepts/organization/store/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/concepts/organization/store/ The developer guide gives some examples of simple interaction with the Store interface, but hides all implementation details, which we will cover here now, at least partially. The store should provide: Read and write access to resources according to the resource Access interface. Transactions, which will guarantee resources that have been read from the database (or query collections) will not change before the transaction is committed. This is provided by the core store module, described in this doc.