https://docs.edgelq.com/build-a-service/declaration/ Recent content in Declaring your service on SPEKTRA Edge Hugo en https://docs.edgelq.com/build-a-service/declaration/specification/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/declaration/specification/ At the beginning of this chapter, before continuing, it is worth first mentioning the naming conventions we use: https://cloud.google.com/apis/design/naming_convention Example api-skeleton for 3rd party app: https://github.com/cloudwan/inventory-manager-example/blob/master/proto/api-skeleton-v1.yaml You can also see API skeletons in the edgelq repository, too. This document describes api-skeletons in bigger detail than a quick startup. When you start writing a service, the first (you have a new, empty directory for your service) you need is to do two things: https://docs.edgelq.com/build-a-service/declaration/protobuf/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/declaration/protobuf/ Protobuf files describe: Resources - models, database indices, name patterns, views, etc. Request/Response object definitions (bodies) API groups, each with a list of methods Service package metadata information Note that you can read about API just all by looking at protobuf files. Example proto files for 3rd party app: https://github.com/cloudwan/inventory-manager-example/tree/master/proto/v1 You can also see files in the edgelq repository too. Resource protobuf files For each resource in the API specification, Goten will create 2 protobuf files: