Description:

Backstage is shifting toward an event-driven system rather than relying solely on periodic refreshes (e.g., in the catalog system). To maintain upstream alignment, this outcome suggests adopting the Events System in RHDH.

Benefits/Value:

There are benefits to going event-driven such as:

1. Near real-time updates

Entities in the RHDH catalog are updated almost immediately after changes occur in the external system. This ensures developers always see the most accurate and current information, without the delays associated with interval-based polling.

2. Efficient, incremental syncing

Rather than performing periodic full syncs, this event-driven approach updates only the affected entities that were actually changed, added, or deleted in the external system.

This results in:

• Fewer API calls, helping avoid rate limits.
• Lower CPU usage, since there is no unnecessary processing.
• Reduced database load because only specific records are modified.

Acceptance Criteria:

• Current upstream event modules should be supported in RHDH.
• Plugins that would benefit from using the events system should start using it and should be supported in RHDH.