Introduce Feature Fallback Strategy

[digitalrisedorset]

Summary

Introduce a fallback strategy for ReactEdge features to ensure that modernisation never compromises platform resilience.

The goal is to allow ReactEdge to incrementally replace legacy PHP features while guaranteeing that every feature has an appropriate degradation strategy should ReactEdge become unavailable or intentionally disabled.

The fallback strategy is not intended to restore the previous level of performance. Instead, it guarantees business continuity while allowing ReactEdge to remain a safe and low-risk modernisation layer.

Objectives

• Define fallback strategies for every ReactEdge feature.
• Classify features according to their business criticality.
• Allow the Health Engine to trigger fallbacks when appropriate.
• Ensure deployments are never blocked by ReactEdge failures or security issues.
• Keep the platform operational while remediation is performed.

Fallback Strategies

No Fallback

Suitable for non-critical user experience enhancements.

Examples:

• USP
• Banner
• Intent Discovery

The feature simply disappears until it becomes healthy again.

---

Static Fallback

Replace the feature with a lightweight static alternative.

Examples:

• Static HTML
• Placeholder content
• Static image
• Informational message

---

Dynamic Fallback

Restore an alternative implementation capable of delivering the required business capability.

Examples:

• Legacy Magento PHP feature
• Simplified server-rendered component
• Alternative JavaScript implementation

The fallback should prioritise availability over performance.

Feature Classification

Each feature should define its fallback strategy.

Examples:

Feature	Critical	Fallback
USP	No	None
Banner	No	None
Intent Discovery	No	None
Product Gallery	Yes	Dynamic
Mini Cart	Yes	Dynamic

Health Engine Integration

The fallback strategy may be triggered by the Health Engine when:

• A critical security vulnerability is detected.
• A feature repeatedly fails health validation.
• A remediation rule determines the feature should be disabled.
• The feature cannot be safely deployed.

The fallback remains active until the feature is considered healthy again.

Principles

• Business continuity takes precedence over feature availability.
• ReactEdge should never become a blocker to deployment.
• Modernisation should remain incremental and reversible.
• Every feature should have a documented resilience strategy.

Future Enhancements

• Automatic fallback activation.
• Configurable fallback policies per installation.
• Progressive feature degradation.
• Automatic restoration once feature health is recovered.
• Health score integration.