A naukri.com initiative
Cloudblog
3w
53
Image Credit: Cloudblog
From Cassandra to Bigtable: Database migration tips from Palo Alto Networks
- Palo Alto Networks migrated their Advanced WildFire product from Apache Cassandra to Bigtable, Google Cloud’s enterprise-grade, low-latency NoSQL database service.
- Palo Alto Networks' Global Verdict Service (GVS), a core component of WildFire, relies on a NoSQL database to process vast amounts of data that needs to be highly available for service uptime.
- Initially, when developing Wildfire, Apache Cassandra seemed like a suitable choice.
- However, as data volumes and performance demands grew, several limitations emerged.
- The migration to Bigtable yielded remarkable results for Palo Alto Networks: 5x lower latency, 50% lower cost, increased availability, simplified architecture, fewer production issues, and enhanced scalability.
- During this phase, continue writing new data to the Cassandra cluster.
- Implement dual writes to Bigtable (along with Cassandra) for all tables.
- Gradually shift read operations from Cassandra to Bigtable by updating the existing application code and/or load balancers.
- Tools for migrating existing data Palo Alto Networks used the following: Use the 'dsbulk' tool for data unloading and Create Dataflow pipelines for loading into Bigtable.
- Adapt your application code to interact with Bigtable's API and leverage its unique features.
Read Full Article
3 Likes
For uninterrupted reading, download the app