[IRS]🌟🚀 Enhancing IRS Scalability to meet required Quantity Model

[mkanal]

Overview

Explain the topic in 2 sentences

IRS is enhanced to achieve scalability according to the required quantity model The objective is to modify the application architecture and infrastructure to handle an increased volume of data, transactions, (and user interactions efficiently), without compromising performance, availability, or reliability.

What's the benefit?

This change increases the efficiency and scalability of IRS by allowing it to handle more transactions and data volume, thus meeting future demand. It also reduces the complexity by identifying and addressing system bottlenecks and optimizing shared components.

What are the Risks/Dependencies ?

• Breaking Change: Changes to the architecture could potentially introduce breaking changes to interfaces or performance.
• Test Environments: Adequate testing in performance and stress testbeds is essential to minimize the risk of underperformance under heavy loads.

Detailed explanation

• Analyze Scalability Limitations of IRS:
  • Evaluation of existing IRS architecture, infrastructure, and database capabilities to identify bottlenecks and areas limiting scalability.
  • Gather data on current performance metrics, including response times, throughput, and resource utilization under various loads.
• Analyze Scalability Limitations of used (shared) components

  • Evaluation of limitations of used shared services

    • EDC
    • dDTR (Decentral Digital Twin Registry)
    • Submodel Servers
• Create Testbeds
  • Create performance and stress test environments to track and measure the efficiency of the implemented improvements. These tests will validate the effectiveness of the architectural changes and ensure no performance degradation.

Current implementation

Proposed improvements

• Transition to a more scalable architecture, which may include load balancing, distributed databases, and horizontal scaling of critical components.
• Optimize the IRS and shared components to reduce latency, improve data flow, and ensure seamless interaction with external systems (EDC, dDTR).
• Implement a mechanism for dynamic scaling based on system load.

Feature Team

Contributor

• Cofinity-X @rogocof
• Cofinity-X @mkanal

Committer

• @ds-jhartmann
• @ds-mwesener
• @ds-lcapellino

---

User Stories

• [IRS] 🌟🚀Efficient orchestration of EDC negotations #931
• 🌟 Limit jobs executed in parallel item-relationship-service#892
• ⭐ IRS Order API for Scalable Job and Batch Delegation item-relationship-service#893

Acceptance Criteria

Scalability Performance:

• IRS system can handle a predefined threshold of data volume and transactions (as per quantity model) without performance degradation.
• The system remains stable under stress and load testing, with response times not exceeding a defined limit

Dynamic Scaling:

• IRS infrastructure dynamically scales to manage varying loads, and autoscaling policies are in place to optimize resource usage based on load fluctuations.
• Scaling mechanisms do not introduce any downtime or service interruptions during peak loads.

Seamless Integration with Shared Components:

• IRS successfully interacts with shared services (EDC, dDTR, Submodel Servers) under high loads, with no critical errors or timeouts in communication.
• Shared services continue to perform efficiently, with their respective response times maintained within acceptable limits during IRS operations.

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Backlog -> Since for Backlog some requirements are missing ... please update them
• Please add missing sections from the feature template, or fill them out
• Please add assignee (overall responsible person who drives the feature)

[mkanal]

Feature is moved from r25.3 to 25.6 due to other priorities.

[stephanbcbauer]

I deleted the milestone, since the milestone is set together in the open planning session. This means ⇾ commitment to work on the feature. THX

[stephanbcbauer]

was not presented in open planning. Nobody was available.