Designing a Yellow Banner System for User Notification During Service Outages

Today Alibaba Cloud experienced an outage, affecting many users; from the symptoms it appears that some components have failed, and the exact details await an official announcement.

When a system goes down and rapid recovery or disaster‑recovery strategies fail, an alternative logic is needed to reduce user impact, which we refer to as the yellow‑banner system.

Yellow banners usually appear at the top or bottom of the user interface, colored yellow to attract attention. They provide feedback on system status, inform users what problem occurred, and suggest how they should respond.

Below is a scenario that uses the yellow‑banner system:

Assume you are responsible for an e‑commerce website. Suddenly the payment‑gateway service encounters an issue, and users cannot complete purchases. In this case we can display a yellow banner to notify users.

The banner might appear at the top of the site with content similar to the following:

"我们目前正在遇到一些支付问题。我们的研发团队正在快速解决。如果您试图购买商品，请稍后再试。很抱歉给您带来的不便。"

In this scenario the banner effectively notifies users of the current problem, that the team is taking action, and gives a clear suggestion – try again later – helping users understand why they cannot complete payment and reducing frustration.

Once the issue is resolved, we can use another yellow banner to inform users:

"我们的支付服务已恢复正常。感谢您的耐心等待。现在，您可以继续您的购物了。"

From this example, the yellow banner serves the following roles:

Provide timely feedback : instantly inform users of system status or operation results, whether success or error.

Guide user actions : give clear instructions, such as asking users to retry later.

Increase transparency : expose internal system state to users, building trust.

Improve user experience : by reducing confusion and frustration, overall satisfaction rises.

Fault notification and solution : deliver error information and guide users on how to cope or wait for resolution.

Based on these functions, how should the system be built? It is essentially a configuration system with some special requirements:

Configurable design : the banner system must be flexible and easy to configure, allowing changes to text, color, display duration, position, etc.

Persistence and timeliness : banners should display according to importance and user needs; some persist until user action, some disappear after a period, and some may be visible only to a subset of users, requiring integration with internal data systems.

Independent deployment : the banner system must be independently deployable and loadable on both front‑end and back‑end, with low change frequency to maintain its independence.

In summary, a yellow‑banner system is a useful tool or contingency plan that, during system failures or service interruptions, provides timely and clear feedback to users, enhances transparency, guides actions, improves experience, and offers notifications and solutions while being configurable, persistent, and independently deployable.

Although the yellow‑banner system has limitations for handling severe outages, it remains a valuable tool for addressing minor or localized failures.