How HashiCorp evolved its cloud infrastructure
Michael Galloway discusses HashiCorp's cloud infrastructure evolution, emphasizing the need for clear objectives, deadlines, and executive buy-in to successfully redesign and expand their services amid growing demands.
Read original article
Michael Galloway, Director of Platform Engineering at Mercari and former Director of Platform Infrastructure at HashiCorp, discusses the evolution of HashiCorp's cloud infrastructure in a recent article. He outlines the challenges faced by HashiCorp's HashiCloud, which initially supported enterprise customers but struggled to accommodate high-security workloads as demand grew. Incremental improvements were insufficient, leading to a need for a complete redesign. Galloway identifies three essential ingredients for successful large projects: a clear objective, a deadline, and executive buy-in.
A clear objective helps teams focus on what matters, while a deadline creates urgency and encourages prioritization. Galloway emphasizes the importance of involving teams in setting realistic deadlines to ensure accountability. Executive buy-in is crucial for overcoming competing priorities and securing necessary resources. He illustrates these principles through the "Western Pioneer" project, aimed at establishing a new disaster recovery region in the US West and expanding to Europe within a year. This project aligned with key business goals, providing the necessary support for the redesign effort.
By prioritizing the project and assembling a knowledgeable team, HashiCorp was able to decompose its existing infrastructure into flexible components, facilitating the creation of new regions. Galloway's insights highlight the importance of strategic planning and collaboration in successfully evolving cloud infrastructure.
Related
Serving a billion web requests with boring code
The author shares insights from redesigning the Medicare Plan Compare website for the US government, focusing on stability and simplicity using technologies like Postgres, Golang, and React. Collaboration and dedication were key to success.
Bad habits that stop engineering teams from high-performance
Engineering teams face hindering bad habits affecting performance. Importance of observability in software development stressed, including Elastic's OpenTelemetry role. CI/CD practices, cloud-native tech updates, data management solutions, mobile testing advancements, API tools, DevSecOps, and team culture discussed.
Are rainy days ahead for cloud computing?
Some companies are moving away from cloud computing due to cost concerns. Cloud repatriation trend emerges citing security, costs, and performance issues. Debate continues on cloud's suitability, despite its industry significance.
Building SaaS from Scratch Using Cloud-Native Patterns
Building a robust Cloud platform for SaaS involves utilizing cloud-native patterns like Google Cloud Platform, Azure, and AWS for self-service, scalability, and multi-tenancy. Diagrid's case study emphasizes control plane design, API strategies, and tools like Kubernetes Resource Model for effective resource management. Joni Collinge advises caution in adopting Cloud-Native technologies to align with specific requirements, ensuring adaptability in a competitive landscape.
The end of the Everything Cloud
AWS is deprecating several lesser-used services under new leadership, focusing on profitability and core offerings. This shift raises concerns about the longevity of new services and customer uncertainty.
3 commentsDude is good at talking and selling. He sells execs on what he wants to do and sells devs on doing and sells everyone on deadlines. OK...
Related
Serving a billion web requests with boring code
The author shares insights from redesigning the Medicare Plan Compare website for the US government, focusing on stability and simplicity using technologies like Postgres, Golang, and React. Collaboration and dedication were key to success.
Bad habits that stop engineering teams from high-performance
Engineering teams face hindering bad habits affecting performance. Importance of observability in software development stressed, including Elastic's OpenTelemetry role. CI/CD practices, cloud-native tech updates, data management solutions, mobile testing advancements, API tools, DevSecOps, and team culture discussed.
Are rainy days ahead for cloud computing?
Some companies are moving away from cloud computing due to cost concerns. Cloud repatriation trend emerges citing security, costs, and performance issues. Debate continues on cloud's suitability, despite its industry significance.
Building SaaS from Scratch Using Cloud-Native Patterns
Building a robust Cloud platform for SaaS involves utilizing cloud-native patterns like Google Cloud Platform, Azure, and AWS for self-service, scalability, and multi-tenancy. Diagrid's case study emphasizes control plane design, API strategies, and tools like Kubernetes Resource Model for effective resource management. Joni Collinge advises caution in adopting Cloud-Native technologies to align with specific requirements, ensuring adaptability in a competitive landscape.
The end of the Everything Cloud
AWS is deprecating several lesser-used services under new leadership, focusing on profitability and core offerings. This shift raises concerns about the longevity of new services and customer uncertainty.