Which tracking software is used by Zomato to track nearby restaurants?

When you’re rolling out something as critical as an NSDL integration/update (for PAN, KYC, or depository workflows), you absolutely need a rollback + comms playbook ready. The key is balancing business continuity (users can still transact/verify) with compliance (regulators don’t get any surprises).

Rollback Plan

• Dual-path deployment
• Keep the old NSDL integration/API path warm in parallel. Don’t decommission it right away.
• Use a config/feature flag toggle so you can switch traffic back in minutes.
• Graceful fallback
• For PAN/KYC checks → route back to cached data or the old API if the new roll-out starts spiking latency.
• For depository actions → queue requests and replay them once stable, instead of hard-failing.
• Rollback triggers
• Define thresholds: e.g. >5% failures or >2x latency sustained for 15 minutes = automatic rollback.
• Have automation ready (scripts, pipelines) so rollback isn’t a manual firefight.
• Snapshot state before cutover
• Capture config, mapping tables, and last successful sync state.
• That way, if you roll back, you don’t lose track of partially processed filings.

Comms Plan
Internal

• Pre-rollout: brief Ops/Support teams that a new NSDL path is going live, and how to identify related errors.
• During rollback: notify on-call + product teams via Slack/Teams channel with: Rolling back NSDL rollout due to X% failure. ETA: 10 minutes.
• Post-rollback: share metrics showing stability restored.

External (customers/users)

• If visible to end-users (like failed PAN/KYC checks), post a short status message:
• We are experiencing slower than normal verification times due to an infra update. We’ve rolled back and services are returning to normal.
• Keep updates short + timestamped until fully green.
• Regulators/Partners
• If the NSDL roll-out is compliance-linked, have a template mail ready:
• During testing of our NSDL integration update, we detected performance regressions. The update has been rolled back, and all transactions are being processed via the prior stable path. No data loss occurred.

"If you’re rolling out FluxCD and worried about performance regressions (sync loops thrashing, API server load, degraded cluster latency), the smart move is to treat it like any infra rollout: have a rollback path and a comms plan ready before you hit go.

Rollback Plan
Canary rollout first

• Don’t switch your whole fleet to FluxCD on day one.
• Start with 1–2 non-critical clusters or namespaces, measure sync latency + cluster API usage.

Keep old deployment mechanism in parallel

• If you were using Helmfile, Argo, or even raw kubectl apply, don’t rip it out yet.
• Keep manifests/templates in sync so you can flip back with minimal drift.

Quick kill switch

• Namespace-level: delete the FluxCD controllers (flux-system namespace) to stop reconcilers instantly.
• Git-level: freeze by locking or archiving the Git repo branch FluxCD is watching.

Rollback path

• Maintain a last known good deployment manifest snapshot from before Flux took over.
• In case of regressions, redeploy from that snapshot with your old toolchain.

Monitoring gates

• Put SLOs on sync duration, API server QPS, pod scheduling latency.
• If thresholds breach, auto-disable sync via feature flag (e.g. remove cluster from FluxCD config).

Comms Plan

• Internal (Dev/Eng teams)
• Pre-rollout: announce that Flux is going live in pilot scope, what changes in workflow, and what metrics will be tracked.
• During rollout: post regular updates in an #infra or #release Slack channel.
• If rollback happens: clearly state Flux disabled, old deploy pipeline re-enabled, ETA for fix.
• External (if customer-facing impact possible)
• Status page template ready: We are investigating elevated latency due to recent infra change. Rollback in progress.
• Keep updates short but regular (every 30–60 mins).
• Exec/Stakeholder updates
• Non-technical brief: New deployment engine tested, saw API server regression, rolled back to stable. No data loss.
• Share metrics proving rollback restored baseline performance.

Potential change-freeze windows

• Thursday, October 2nd: Mahatma Gandhi Jayanti and coincides with Dussehra.
• Saturday, October 11th - Sunday, October 12th: October 11th is a regional holiday in many states, Saturday and October 12th is a Bank Holiday across all of India for Dussehra.
• Monday, October 20th: Diwali/Deepavali

As of late September 2025, you should avoid enabling new features during the following change-freeze windows:

• Early-to-mid October: Avoid deployments during the first two weeks of October, especially around the major festival periods for Dussehra and Diwali.
• Late November to December: Initiate a company-specific change freeze to avoid potential site disruptions during the holiday shopping season, including Black Friday and Cyber Monday.

Rollback plan
The most effective rollback for a Dependabot-induced performance issue is to pause the service, not revert the codebase. This immediately stops new update PRs and prevents further performance impact while you investigate.

• Phase 1: Detection and immediate action
• Phase 2: Containment and analysis
• Phase 3: Relaunch

Communications plan
Transparent, clear communication is essential during a performance regression. It reduces developer anxiety and maintains confidence in the automated system.