An online retailer uses a hybrid cloud to handle burst capacity. Which part of the application is most likely to be sent to the public cloud during a demand peak?

In the context of a hybrid cloud used by an online retailer to manage burst capacity, the warehouse module is a strategic choice for offloading during demand peaks. The reason for this lies in the nature of operations during high traffic periods.

The warehouse module primarily deals with inventory management, indicating stock levels and locations within various warehouses. During peak demand times, the retailer may experience a high volume of orders, necessitating quick access to updated inventory data to fulfill these orders efficiently. Offloading this module to the public cloud allows it to scale dynamically, accommodating fluctuations in demand without impacting the performance of other critical functions.

On the other hand, modules involving sensitive information such as payment details or shipping addresses are typically kept on private infrastructure due to security and compliance concerns. Handling credit card information, for instance, requires strict adherence to regulations like the Payment Card Industry Data Security Standard (PCI DSS). Thus, placing these modules in the public cloud could expose the retailer to compliance risks.

Therefore, leveraging the public cloud for the warehouse module during peak times aligns perfectly with the need for flexible capacity management while maintaining the integrity and security of customer information elsewhere in the application.