Loading post…
MongoDBProblem & solution
How Palo Alto Networks Built a Zero
Summary
Palo Alto Networks built a new SASE Health Portal to provide real-time service health visibility for its enterprise customers. The previous architecture relied on relational databases and cloud data warehousing, which caused schema migration bottlenecks and regional lock-in. To solve this, the team deployed containerized services across multiple cloud zones in an active-active configuration. They used MongoDB Atlas as a globally replicated database, enabling automated cross-region failover and flexible document modeling for customer subscriptions. The new portal eliminates alert fatigue by allowing granular subscriptions and achieves zero relational joins for fast incident matching.
Context
Palo Alto Networks needed a resilient service health status portal for its Prisma SASE platform, which secures one-third of the Fortune 500. The legacy relational database architecture caused schema migration bottlenecks and fate-sharing with a single cloud region, risking portal downtime during outages.
Approach / What changed
The team deployed containerized application services across multiple geographically isolated cloud zones in active-active configurations on Kubernetes. They used MongoDB Atlas as a globally replicated database spanning three distinct geographical zones, with automated cross-region replication and failover. They also moved from relational tables to MongoDB’s flexible JSON document model for customer subscription profiles.
Takeaways
MongoDB Atlas’s automated cross-region replication and failover enables the SASE Health Portal to survive a total regional outage without dropped connections or manual intervention.
Using MongoDB’s flexible JSON document model eliminated expensive ALTER TABLE migrations and JOIN queries, allowing frictionless onboarding of new security services with zero downtime.
The new subscription engine uses single self-contained documents per user, enabling notification microservices to match incoming incidents to customer profiles in microseconds.
FAQ
How does the portal survive a regional cloud outage?
MongoDB Atlas is deployed across three distinct geographical zones with automated cross-region replication. If the primary zone fails, MongoDB's automated failover promotes a secondary node in another region to primary, and the application continues reading and writing without dropped connections.
How does the portal reduce alert fatigue for customers?
The subscription engine uses MongoDB's flexible document model to let customers subscribe only to the precise products, components, and geographic regions that impact their business. This prevents inundation with alerts about localized issues on other continents.
What was the main problem with the previous relational database approach?
The relational architecture required expensive schema migrations (ALTER TABLE commands) for every new service or subscription tier, risking table locks during high traffic. It also tied the portal's availability to a single cloud region, violating resilience principles.
Source and freshness
- Source
- mongodb.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.