Kindred Group and LUSH have very different deployments of CockroachDB. But they both arrived at the need for a distributed SQL database for similar reasons.
At a recent Meetup at LUSH Labs in London, engineers at LUSH and Kindred Group presented to a group of CockroachDB users about their experiences–and configurations–of CockroachDB.
Here’s a recap of what they’ve learned so far.
Kindred uses geo-partitioning to automate data regulatory compliance
Kindred Group, plc is one of the world’s leading gaming companies, with more transactions per year than PayPal. As a global company, Kindred needed a solution that would provide low latency to users across the world, while also automating Sanjoy Roy, Architect at Kindred Group, spoke about how their implementation of CockroachDB is easing the pains of operating a global business with geo-partitioning.
For more on Kindred Group’s deployment of CockroachDB, read the full case study.
LUSH is migrating from Google Spanner to CockroachDB
Similarly, LUSH turned to distributed database solutions to help with supply chain management, data sovereignty protection, and improved resiliency. Their current way of solving these problems? Google Spanner. But Rob Reid, principal engineer at LUSH digital, spoke about why the company is turning away from Spanner and towards CockroachDB. Spanner is a black box solution that can only run on Google’s atomic clocks. In addition, exporting data out takes a very specific skillset, including knowledge of binary Avro.
While LUSH is still in the initial phases of the migration, they presented about the steps they’re taking in production to migrate, and what that migrate entails. Interested in coming to our next tech talk at the Lab? Check out our events calendar.