The brightwheel engineering team was a big Heroku customer, and relied extensively on Heroku's Redis offering. We loved how simple it was to spin up and use a redis instance on Heroku, and in the early days, the basic monitoring tools that Heroku provided were more than enough to get us off the ground. Brightwheel's reliance on Redis continued to grow as we scaled the service, and over time, we had to build our own profiling and querying tools to debug issues and monitor performance.
I just finished The Unicorn Project by Gene Kim. This book is the sequel to The Phoenix Project, and is told from the point of view of a female Individual Contributor at the same company, and at the same time as The Phoenix Project. Both books do a great job educating the reader about foundational business and technical principles while telling a fun story about a retail company struggling with its digital transformation.
This year at AWS Re:Invent, the AWS container engineering team released a feature that I'd been eagerly awaiting. AWS EKS on Fargate. EKS on Fargate is an expansion of AWS's Managed Kubernetes Service, but removes the need to spin up and manage your own EC2 instances and autoscaling groups. This is a big deal for a couple of reasons. Fargate eliminates the need for customers to create or manage EC2 instances for their Amazon EKS clusters.
Jan 17, 2019 - Goodbye, brightwheel Whenever we sent an offer to a prospective employee at brightwheel, we’d ask everyone at the company to send them a welcome email. The point was to let our prospective employees know how excited we were that they received an offer, and how eager we were to have them join our team. Teammates who chose to join us, and even those that didn’t, all said that those emails made them feel like they were joining a close knit group, where their contributions would be valued.
Jan 13, 2019 - Update Q4 Books The DevOps Handbook Over the last 4 years at brightwheel We’ve been really lucky so far to be able to leverage a popular PAAS (platform as a service) solution to manage a large amount of our infrastructure needs, but now, we need to start implementing some of the practices outlined in the DevOps Handbook to scale up our infrastructure and engineering teams. For some engineers especially those in Silicon Valley, some of the practices outlined will be self-evident.