5th November 2026
Academic Concepts
- Cloud Computing and Service Models: Understanding cloud infrastructure, scalability, availability, and dependence on cloud service providers.
- Business Continuity and Disaster Recovery: Concepts of backup, disaster recovery, Recovery Time Objective (RTO), and Recovery Point Objective (RPO).
- High Availability and Fault Tolerance: Use of redundancy, multi-region deployment, failover mechanisms, and resilient cloud architectures.
- Multi-Cloud and Hybrid Cloud: Comparing single-cloud, multi-cloud, and hybrid approaches for reducing vendor dependency and improving resilience.
Learning Notes
- Cloud computing provides flexibility and scalability but does not eliminate the risk of service outages.
- Data backup alone cannot ensure business continuity; organizations need tested recovery mechanisms and alternative infrastructure.
- Critical business applications should be identified and prioritized during disaster recovery planning.
- Effective cloud management requires a balance between cost, availability, security, performance, and business requirements.
Learning Outcomes
After studying the caselet, students will be able to:
- Analyze the technical and business impact of a major cloud service outage.
- Evaluate different cloud strategies, including single-cloud, hybrid-cloud, and multi-cloud approaches.
- Design appropriate business continuity and disaster recovery measures for cloud-based applications.
- Recommend a suitable cloud resilience strategy by considering cost, security, availability, and organizational requirements.
Course Relevance: PGDM, MCA, BCA
Case Setting
Ananya Rao was sent a message on a Monday morning at 9:05 a.m. that she never thought she would receive.
Sorry, we can’t provide the application at this time. “Our tech team is investigating the issue.”
Ananya didn’t take the message seriously at first. She was Chief Operating Officer at FreshKart, an online grocery company based out of Bengaluru, which was growing at a rapid pace. FreshKart had more than 1.5 million registered customers and delivered groceries, household products and daily essentials to customers across various Indian cities. Like many businesses today, FreshKart depended heavily on cloud computing.
The company’s website was hosted on the cloud. It built its mobile application on cloud infrastructure. They used cloud-based services to store customer information, product catalogs, order details, payment records and delivery details. Even the company’s internal dashboards were tied to cloud apps.
FreshKart had proudly called itself a “cloud-first company.” That phrase had sounded like a strength all along. And this Monday morning, all of a sudden, it was sounding like a weakness.
- Monday Morning Mystery Monday was typically FreshKart’s busiest day.
Customers would order their groceries before they went to work. Restaurants were buying every kind of supply. Corporate clients requested refreshments, drinks and workplace supplies.
The customer service department began taking calls around 9:15am. The application will not run.
- I didn’t get my order.
- I completed the transaction but did not receive an order confirmation.
- Representative from delivery informs me my order does not exist.
- Employees initially thought the problem was limited to the mobile app.
- IT Support staff rebooted some services.
It was all the same. The technology team identified serious connectivity problems with numerous cloud services used by FreshKart at 9:25 AM.
Immediately the company CTO, Rahul Menon summoned an emergency meeting. “Is our app down? Ananya inquired.
“You there?” Rahul paused.
“Some places the app is working but our main cloud services are not working properly.”
How long will it take to fix?
We don’t know at this time.
Ananya was worried by the answer.
- Reasons behind FreshKart’s Transition to Cloud Computing.
Five years prior, FreshKart was a far smaller enterprise. The IT infrastructure was situated in a tangible data center in Bengaluru. The organization maintained its own servers, networking apparatus, storage systems, and backup infrastructure.
At that period, FreshKart had a workforce of around 100 individuals and conducted operations in two urban areas. As the organization expanded, its technology demands also increased. During major festivals and promotional campaigns, website traffic can surge by five to six times within a few hours.Physical servers must be maintained in adequate quantities during peak periods. The technical staff of FreshKart suggested transitioning to cloud computing.
The reasoning was clear.
- Rather than purchasing servers for the anticipated maximum workload, the firm might utilize cloud resources on demand.
- Should customer traffic rise, additional computing resources may be allocated.
- Should traffic diminish, the firm might reduce its utilization.
- The administration was enamoured with that concept.
Gradually, the firm transitioned much of its infrastructure to a prominent public cloud provider. The process required nearly eighteen months to complete. At the conclusion of the relocation, FreshKart possessed almost no exclusive physical infrastructure. The board deemed the relocation a significant triumph. The organization initially reduced its expenditure on technology. The IT department was not required to acquire servers periodically. Programmers could facilitate the expedited deployment of novel services. New staff can be granted access to programs without the necessity of installing intricate infrastructure. The cloud facilitated FreshKart’s expansion into additional cities. The fundamental concept was never challenged:
What would occur if the cloud experienced a failure?
- A Comfortable Dependence
Over time, FreshKart increasingly depended on its cloud service provider. However, the reliance extended beyond just server hosting. The firm employed cloud computing services for:
- Hosting applications
- Database architectures
- Verification of customer identity
- Repository facility
- Monetary exchange services
- Examination of data •
- Monitor your consignment
- Employee correspondence
- Secured against duplication
- Supervision
- Information processing
- Corporate analytics
The technological framework has grown intricate. Services were interlinked with one another.
For instance, upon a client’s order, the subsequent action resembled the following:
Client Application Verification -Product Repository -Order Administration -System Payment – Processing Gateway – Inventory Control – System Delivery Framework -Customer Notification System
The majority of these components depended on cloud infrastructure. If a single service becomes unresponsive, it may impact additional services. The system was designed for optimal performance. It was not engineered to handle a complete cloud failure.
- The Initial Two Hours
At 10:00 a.m., FreshKart’s customer service center was overwhelmed.
Typically, there were approximately 300 client questions recorded between 9:00 a.m. and 10:00 a.m. On that morning, they had more than 2,000 calls. The clients expressed dissatisfaction. Certain individuals have incurred charges, however were unable to view their orders. Occasionally, orders were submitted twice due to the initial effort seeming unsuccessful. The delivery personnel awaited instructions. The warehouse personnel were unable to access the revised order listings. The financial division was unable to manage the disbursements. The marketing department had arranged the promotional campaign for 10:30 AM. The initiative had to be terminated.
Ananya gazed at the issues, which continued to escalate.
Is there an alternative system?
Rahul stated, ‘We have acquired the info.’
That does not pertain to my inquiry.
Rahul hesitated momentarily. We lack a comprehensive backup solution that can be activated instantaneously. Ananya comprehended the issue. FreshKart possessed backups. However, backups did not equate to business continuity. Backup differs from business continuity. The FreshKart management has repeatedly been guaranteed that its information was secure. The organization consistently performed backups. Some executives thus concluded that the organization was safeguarded.
However, the turmoil also revealed a significant disparity. A backup allows for the retrieval of data. A business continuity framework guaranties operations persist despite the primary system’s failure. The primary emphasis of FreshKart was predominantly on the former. It had insufficiently invested in the latter.
Rahul briefed the emergency management team on the current situation.
We possess entry to our supplementary database. Nonetheless, the necessary infrastructure must be established prior to the application functioning effectively.
What is the duration? What is that?” inquired Ananya.
A minimum of many hours.
Shall we allocate a few hours?
No response was received.
- The Commencement of Economic Impacts
At 11:30 am, the financial department of FreshKart compiled a preliminary evaluation. He stated that it was incurring a loss of approximately ₹18-20 lakh each hour. However, declining sales were not the sole issue.There were supplementary expenses. Certain clients had previously received invoices for orders that remained unverified.
FreshKart is obligated to reimburse certain amounts. Delivery personnel are poised for directives. Storage facilities were not functioning at their maximum capacity. Customer care representatives were putting in more hours. The firm indicated that numerous corporate clients were anticipated to want indemnities.
The finance director estimated the direct expenses of the company’s disruption during a 24-hour period to range from ₹4 crore to ₹5 crore. The indirect expense could be significantly greater. FreshKart has established a reputation for dependable delivery throughout the years. A singular significant failure can obliterate client confidence.
- The Technology Team Explores Alternatives
By noon, Rahul’s squad possessed three alternatives.
Option A:
Anticipate the Cloud Service Provider. The most straightforward approach was to exercise patience. A significant technical team was resolving the problem at the cloud service provider. The IT department of FreshKart had limited control over the essential infrastructure. Any delay would alleviate additional technological hazards. Nevertheless, the precise schedule for the reinstatement of the service was still uncertain.
It might necessitate an extra hour. This could necessitate a period of twelve hours. It may necessitate a specific period.
Option B:
Transfer critical applications to a different cloud environment. FreshKart has occasionally contemplated multi-cloud strategies. Nevertheless, it has never achieved a single one. The company utilized a different cloud provider for specific minor tasks.
The question was if the critical systems could be transferred there. Rahul’s team promptly determined that the resolution was complex. The applications were intricately connected to the offerings of the main cloud provider. Translocating them would represent a restructuring. Some databases may ecessitate migration. You must reinstate the security settings.
I need to establish network connections. The organization has not previously evaluated the entire process. Engage the Legacy Data Center FreshKart preserved a segment of its traditional servers. They were preserved for the sake of historical documentation.
Ananya posed a question:
Is it feasible to recover the former data center?
The infrastructure manager seemed ill at ease. We possess the ability to activate specific systems, however the previous environment is considerably more limited than our present one.
What portion of the business can it maintain?
Approximately 15-20% of our standard operations.
That was inadequate for the optimal operation of FreshKart. A limited service can be adequate.
- A Difficult Choice
1 p.m. Ananya had a tough call to make. The firm can wait until the cloud service provider is ready to act. It might be looking for a deadly emergency move. If it goes wrong, the migration can make problems worse. But doing nothing can be harmful too.
Rahul was asked a simple inquiry by her.
“Can you move only the critical services, to the legacy infrastructure, and keep the business alive?”
Rahul thought.
Yes. But it won’t be Freshkart in the way customers think about it.
What else could we do?
Basic Shipping Information Important Product Information Client Access Selected Ordering Functions.
What would we forego doing?
A few marketing features, a few non-essential services, extensive analytics, personalized recommendations. Ananya considered the concept. FreshKart needn’t have been magical. It had to function.
- Emergency mode
FreshKart declared at 2:00 p.m. that company has entered Emergency Operations Mode. The company shifted its priorities.
The technical team has given three different types of apps.
Required
The first services to be restored included:
- Customer identification validation • Purchase
- Confirmation of payment
- Shares information
- Delivery Information
These services could be reestablished later:
- | Client Testimonials • Marketing Funds
- Full analysis .
- Loyalty rewards
Non-essential services may be unavailable.
- Internal analytics UI Chronological sequence of accounts
- Sophisticated customer segmentation
- A slate of applications for jobs
This classification allowed the tech team to focus on the most crucial things. They concentrated on retaining the essential functions, instead than trying to get everything back.
- Integration of Staff within the Rehabilitation System
The upheaval additionally exposed another flaw.
FreshKart has devoted considerable funds to technological advancements however has inadequately prioritized employee training for potential major technology disruptions.
A uniform procedure was lacking for customer support agents to implement when a customer’s payment was successful yet their order failed to materialize. Employees in the warehouse were indecisive on the continuation of their preparations.
The delivery agents were doubtful regarding the reliability of the information they had received. Supervisors initiated the formulation of provisional spreadsheets. A number of teams initiated the use of messaging platforms for the transfer of information. That brought forth a fresh peril.
The organization was rectifying one dilemma and simultaneously producing another. Informal outlets revealed confidential consumer data.
Meera Shah, serving as the Chief Information Security Officer, immediately alerted the management team. We should proceed with care. An interruption does not justify overlooking safety protocols. She demanded rigorous rules. Only individuals with authorization are permitted to utilize provisional systems for sanctioned data. Messaging applications are prohibited from conveying client payment details. Temporary files must be eradicated following the recovery procedure. Every manual transaction necessitated documentation. The dilemma was evolving into both a managerial and a technological issue.
- The Cost of Humanity
As night approached, the personnel were fatigued. Customer support representatives were managing irate clients. Warehouse personnel were conducting inspections of the orders. The technology staff had been working diligently since early morning. Certain employees had not had sufficient respite.
The Human Resources department organized catering services and additional staff. The Chief Executive Officer disseminated an internal communication:
“Our clients are shouldering the issue. Our personnel are shouldering the responsibility. Kindly assist them. “
The impact of the communication was instantaneous. Individuals were being reassigned from other divisions to assist customer service. Payments were balanced with the assistance of financial staff. The logistics team arranged the deliveries. The crisis surprisingly united various.
- Restoration via Cloud Service Provider
The cloud service company announced at 7:45 p.m. that it was “methodically reinstating services. The technology staff at FreshKart commenced efforts to reestablish the systems. However, the organization did not promptly resume standard operations.
What is the reason?
Reverting to outdated systems is invariably perilous.
The team needed to be assured:
- Synchronization of the database • Assessment of order duplication
- The precision of transaction records
- Precision of stock data
- The functionality for customer notifications was assessed.
- The precision of the delivery details.
The team resolved against executing a full rollback. They progressively reinstated services.
- Initial Day
By approximately 11:00 p.m., 14 hours following the onset of the problem, FreshKart successfully reinstated nearly 80% of its standard services. The website was operational. Clients were permitted to place orders. The delivery tracking system was operational. Certain services remained inoperative. The organization reported that the circumstances were stable by 6:30 a.m. the subsequent morning. The disruption persisted for almost a full day.
FreshKart accomplished it. However, the management team recognized that mere surviving did not equate to success The enterprise encountered millions in rupees. Several client orders were annulled.
Certain corporate clients inquired whether FreshKart could be deemed a reliable venue for their prospective transactions. The board sought clarification.
- The Assembly of the Board
The FreshKart board convened in an extraordinary meeting three days subsequent to the disruption. The chairman commenced with an uncomplicated inquiry: What prompted this occurrence, why were we chosen? The response was not merely ‘due to the cloud’s failure.’ The cloud service provider experienced a significant disruption.
However, this situation was exacerbated by FreshKart’s own choices. The board recognized several issues.Excessively Dependent on a Sole Supplier. The majority of essential services relied on a sole cloud provider. Incomplete Catastrophe Remediation The organization possessed backups but lacked a thoroughly validated alternative environment.
Unprepared for Multi-Cloud
The organization had discussed multi-cloud computing, although had not implemented it for essential applications.
Inadequate Recovery Assessment
The catastrophe recovery protocols existed in documentation, although had not undergone evaluation in a practical setting.
Insufficient Staff Instruction
Staff were uncertain about how to react during a significant technological breakdown.
Overconfidence in Cloud Dependability
The administration believed that due to the cloud provider’s substantial size and expertise, significant disruptions would not adversely affect the firm.
- The Revised Proposal
Rahul suggested a rehabilitation strategy. He suggested that FreshKart allocate ₹6 crore over the next two years to enhance resiliency.
The intention was to incorporate:
- An additional cloud ecosystem
- Enhanced disaster recovery capabilities
- Automated backup systems
- Consistent evaluation of recuperation
- Enhanced surveillance
- Deployment of mission-critical apps across many regions
- Personnel training
- Exercises for business continuity
- Enhanced cloud security
- An official strategy for exiting the cloud.
Immediately, the finance director encountered difficulties. Six crore constitutes a substantial sum of money.
- The Inquiry Regarding Multi-Cloud.
Multi-cloud computing emerged as one of the most discussed concepts. Several directors believed that FreshKart ought to utilize two major cloud service providers. The reasoning was rudimentary. If one supplier faltered, the alternative could assume control.
However, certain others. They contended that a multi-cloud approach would introduce intricacy. Applications must be engineered to function across many settings. Personnel must acquire new competencies. It would complicate oversight. The intricacies of security management would increase. Expenses may also increase.
The Chief Technology Officer proposed an alternative strategy.
- FreshKart might discern its paramount applications and strategize for portability, instead of consolidating everything onto two cloud platforms.
- The organization could execute its standard operations on its main cloud service provider, while preserving a validated recovery infrastructure in a different location.
- This is more economical than replicating everything.
- However, it would still offer a degree of protection.
- The Inquiry of the Chief Executive Officer
At the conclusion of the discussion, the CEO of FreshKart posed a final inquiry to the management team: Should FreshKart be reliant on the cloud or simply utilize cloud capabilities? No one responded right away. The disparity was considerable. The organization depends on the cloud, hence supposing its perpetual availability. A cloud-enabled enterprise utilizes cloud technology while also having a contingency plan for instances when the cloud is inaccessible.
FreshKart had acquired this understanding through difficult experiences. The organization saw rapid growth and effectively utilized cloud computing. The cloud has contributed to reducing infrastructure expenses. It exhibited superior scalability. It had catalyzed creativity.
However, the disruption revealed an additional reality: Ease fosters reliance. FreshKart needed to ascertain the degree of reliance it was prepared to tolerate.
- The Decision We Confront
The management team ultimately devised three potential strategies.
Approach A –
- Preserve the Existing Conditions
- Preserve the existing cloud infrastructure.
- Enhanced surveillance and data recovery systems.
- That would be the most economical option.
- Nonetheless, the organization would continue to rely significantly on a sole supplier.
Strategy B –
Combined Disaster Recovery
- Sustain the principal cloud infrastructure and establish a secondary recovery environment utilizing either an alternative provider or the organization’s own resources.
- Essential services may be reinstated amid significant disruptions.
- This would be a rather low-cost investment.
Strategy C –
- Architecture for Complete Multi-Cloud Integration 100%
- Redesign essential applications to operate across several cloud service providers.
- That would provide greater autonomy.
- However, it would also represent the priciest and most technically intricate alternative.
The board requested Rahul to provide a comprehensive recommendation. Ananya needed to consider the ramifications for the firm. Meera was requested to conduct a security risk evaluation. Subsequently, they requested the finance director to calculate the long-term expenses. The resolution will establish the framework for FreshKart’s technological approach throughout the forthcoming five years.
- The Majestic Blueprint
However, FreshKart was not solitary in its endeavor. Companies across several sectors are increasingly transitioning their operations to cloud platforms.
- Financial institutions utilize cloud technology.
- Medical facilities are utilizing cloud technology.
- Cloud Solutions for Higher Education Institutions.
- Retailers utilize the cloud.
- Authorities utilize cloud technology.
- Cloud computing is an ally for the start-up.
- Cloud computing provides adaptability, extensibility, and rapidity.
However, as an increasing number of company operations transition to the cloud, the significance of resilience escalates. A cloud service disruption does not imply that cloud computing is an unwise option. Rather, it poses a more significant inquiry: Has the organization configured its cloud infrastructure according to the risk tolerance it is prepared to accept?
FreshKart constructed its infrastructure mostly for standard conditions. The disruption prompted the organization to consider unusual circumstances.
The organization had solicited:
- What strategies can we implement to expedite cloud expansion?
- Subsequent to the disruption, it began to pose an alternative inquiry:
- How can we maintain operations when the cloud fails?
That inquiry would delineate the forthcoming phase of FreshKart.
Discussion Questions
- Identify the major reasons for FreshKart’s vulnerability during the cloud outage.
Discuss the technical and managerial factors that contributed to the impact of the outage.
- Should FreshKart adopt a multi-cloud strategy?
Compare the advantages and disadvantages of staying with a single cloud provider, adopting hybrid disaster recovery, and adopting a full multi-cloud architecture.
- “Backup is not the same as business continuity.” Explain this statement using the FreshKart case.
What additional measures should FreshKart implement to ensure that critical business operations can continue during a major cloud failure?
- If you were the CTO of FreshKart, which five cloud-resilience measures would you implement first?
Justify your choices based on cost, business criticality, recovery time, security and scalability.
- “The cloud did not fail FreshKart; FreshKart failed to prepare for cloud failure.” Do you agree?
Critically evaluate this statement and explain how organizations should balance cloud convenience, cost, reliability, vendor dependence and business continuity.
