Loop Segments overview
When a loop contains multiple microservices, you can add loop segments to manage each microservice independently. Each segment creates a dedicated set of resources and integrations for that microservice.
These resources support the development lifecycle of the microservice and can include items such as:
- A dedicated control repository
- A separate plan component
- Supporting test and build integrations
Each segment behaves like a sub-loop and provides capabilities that are specific to a microservice.
A segement:
- Supports its own build and validation flow
- Tracks changes specific to the microservice
- Remains connected to the overall application lifecycle
You can use segments when you are working with multiple microservices in a single application, each microservice needs separate repositories, builds or testing processes. Segments help maintain clear separation between microservices without creating multiple loops for each microservice.
For example: You build an e-commerce application using a microservices architecture, such as frontend service, order service, and payment service. All these microservices belong to the same application and share a common delivery lifecycle, so you create one Loop to represent the overall application. However, you create a Segment for each microservice inside the parent loop. For example, you create a segment named Order Service.
A loop can contain multiple segments and each segment contributes to the overall value stream.