Foundation · 2 min
What you need to know
What is graceful degradation?
Graceful degradation means keeping the essential service usable while a failed or overloaded optional feature is reduced, replaced or temporarily hidden. Operators should still receive the error.
Which ecommerce features are critical vs optional?
Critical features are needed to understand products, calculate a valid order, pay safely, and receive trustworthy confirmation. Optional features may include recommendations, chat, rich reviews, or personalization, depending on the store.
Should checkout fail if analytics is unavailable?
No. Analytics failure should be recorded and repaired, but it should not stop a valid checkout or duplicate a payment. Use independent monitoring to detect the measurement gap.
Should product pages fail if recommendations are unavailable?
No. Show the product page without recommendations and preserve the main product, price, availability, and buying controls. Leave reserved space only if it does not confuse or delay the shopper.
How should optional service failures be handled?
Optional services should have short timeouts, isolated resources, and an empty or simplified fallback. Track the failure, but do not repeatedly retry in a way that overloads the essential journey.
A quick store check
Turn off one optional dependency in a test environment and confirm that browsing, cart and checkout remain usable.
Foundation · 2 min
Frequently asked questions
Is hiding an error the same as graceful degradation?
No. The customer needs a safe usable alternative, while the technical failure remains visible to operators.
Should recommendations use stale data during an outage?
Only when the data remains safe and useful; otherwise remove the module instead of showing misleading products.