Swiggy's blog serves as a platform for industry insights, covering a wide range of topics such as emerging food delivery trends, consumer preferences, market analysis, and innovations in the food service sector. Through  articles, case studies, and interviews with industry experts, Swiggy offers  knowledge and actionable strategies for restaurant owners, food entrepreneurs, and stakeholders in the food delivery ecosystem. Readers can learn about effective marketing techniques, operational best practices, customer engagement strategies, and technology advancements shaping the future of food delivery services.

Swiggy Bytes

Swiggy's engineering team shares how they migrated multiple B2B dashboards from a fragmented S3-per-app architecture to a unified Module Federation 2.0 setup. The post covers the full journey: eliminating ~638 KB of duplicate JavaScript per remote app, solving singleton traps (styled-components loaded twice), synchronizing React Router with TanStack Router via memory history, and implementing a cache-busting strategy for remoteEntry.js. The most complex challenge was migrating thousands of authenticated users to a new domain without forced logouts — solved using a popup window + postMessage approach to bypass browser third-party storage partitioning, rolled out in 4 phases from soft nudge to permanent 301 redirect. Also covers config-driven version pinning for sub-5-minute rollbacks and ImageKit integration for image optimization.

The Micro-Frontend Evolution: Why We Traded S3 Behaviors for Module Federation (and What It Cost Us)

The Domain Migration: Shifting Traffic Without Forced Logouts

Get anurag shahi ’s stories in your inbox

The Solution: /migration-bridge + Popup Window + postMessage

Why Popup, Not Iframe? (The Trap We Almost Fell Into)