https://docs.edgelq.com/build-a-service/operation/ Recent content in Operating your service on SPEKTRA Edge Hugo en https://docs.edgelq.com/build-a-service/operation/deployment/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/operation/deployment/ Once the service is developed well enough, you can deploy it. Quick visual recap is (regional deployment): The large block on the right/top side (most of the image) is the SPEKTRA Edge-based service. Below you have various applications (web browsers or Edge agents) that can communicate with service or core SPEKTRA Edge services (left). Service backend deployment is what we focus on in this part. The blue parts in this block are elements you had to develop, three different binaries we discussed in this guideline. https://docs.edgelq.com/build-a-service/operation/migration/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/build-a-service/operation/migration/ When we talk about Service versioning, we don’t mean simple cases like adding new elements: Adding a new field to an existing request/response/resource, as long as it does not destroy old logic). Removing a field from existing request/response/resource, as long as backend service does not need it). These operations can be done simply from protobuf files. message SomeRequest { string old_field_a = 1; int32 old_field_b = 2; // We can add new field just by assigning new proto wire number to it: repeated int32 new_array_field = 3; } This is an example of how to properly remove a field