<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Developing your service on SPEKTRA Edge</title>
    <link>https://docs.edgelq.com/build-a-service/development/</link>
    <description>Recent content in Developing your service on SPEKTRA Edge</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.edgelq.com/build-a-service/development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Implementing your service</title>
      <link>https://docs.edgelq.com/build-a-service/development/service/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/build-a-service/development/service/</guid>
      <description>Full example of sample service: https://github.com/cloudwan/inventory-manager-example&#xA;Service development preparation steps (as described in the introduction):&#xA;Reserving service name (domain format) using IAM API. Creating a repository for the service. Install Go SDK in the minimal version or better, the highest. Setting up development - cloning edgelq, goten, setting env variables. In your repository, you should first:&#xA;Create a proto directory. Create a proto/api-skeleton-$VERSION.yaml file Get familiar with API Skeleton doc and write some minimal skeleton.</description>
    </item>
    <item>
      <title>Developing your business logic in the controller</title>
      <link>https://docs.edgelq.com/build-a-service/development/controller/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/build-a-service/development/controller/</guid>
      <description>API Server can execute very little actual work - all reading requests are limited in size, they can fetch a page. Write requests will stop working if you start saving/deleting too many resources in a single transaction. Multiple transactions will also make users wonder if something is stuck. Some actions are intense, for example, when a user creates a Distribution resource in applications.edgelq.com, that matches thousands of Edge devices, the system needs to create thousands of Pod services.</description>
    </item>
    <item>
      <title>Registering your service with the SPEKTRA Edge platform</title>
      <link>https://docs.edgelq.com/build-a-service/development/registration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/build-a-service/development/registration/</guid>
      <description>While goten provides a framework for building services, SPEKTRA Edge provides a ready environment with a set of common, pre-defined set of services. This document describes a selected set of specific registrations needed by the developer, other services can and should typically be used with the standard API approach.&#xA;Integration with SPEKTRA Edge is practically enforced/recommended on multiple levels:&#xA;Your service needs to register itself in meta.goten.com, otherwise it can&amp;rsquo;t simply work.</description>
    </item>
    <item>
      <title>Developing the sample service</title>
      <link>https://docs.edgelq.com/build-a-service/development/sample/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/build-a-service/development/sample/</guid>
      <description>When writing code for your service, it is important to know some Goten/SPEKTRA Edge-specific components and how to use them. This part contains notable examples and advice.&#xA;Some examples here apply to edge runtimes too, as they often describe methods of accessing service backends.&#xA;Basic CRUD functionality Unit tests are often a good way to show the possibilities of Goten/SPEKTRA Edge. While example service implementation shows something more &amp;ldquo;real&amp;rdquo; and &amp;ldquo;full&amp;rdquo;, various use cases in the shorted form are better represented with tests.</description>
    </item>
  </channel>
</rss>
