bwarminski

3 ms·

1. 1.▲
   by bwarminski 3y ago

   I am a part of Olga's team and would be happy to answer any questions. This undertaking was highly successful and has become the new model for implementing Vitess cluster-wide changes. Previously, such changes involved cumbersome in-pl
2. 2.▲
   How HubSpot Upgraded a Thousand MySQL Clusters at Once(product.hubspot.com)

   27 points by bwarminski 3y ago|2 comments
3. 3.▲
   by bwarminski 4y ago

   No worries, happy to share more details. For the databases where performance is a concern, we use constraints and reservation requests to all but guarantee it will be the only tenant on the node and we actively monitor CPU throttle and will
4. 4.▲
   by bwarminski 4y ago

   This article does a great job describing the investment required to pull this off. At HubSpot, my team is running a large Vitess/MySql deployment (500+ distinct databases some sharded, multi region) atop k8s today and had to learn a lo
5. 5.▲
   by bwarminski 8y ago

   We're using Argo as a replacement for our GoCD based continuous delivery system and it's been fantastic. We were about to move onto Concourse and realized we would need to set up the and manage the equivalent of a Kubernetes clust
6. 6.▲
   Introducing Exploranda, a set of tools for exploring complex systems(eng.localytics.com)

   1 points by bwarminski 9y ago|0 comments