Suggestions
Asanka Jayasuriya
CTO 8VC, Advisor, Investor
Asanka Jayasuriya is a distinguished professional in the field of cloud engineering, with vast experience and a diverse background.
Having studied Computer Science at the University of Toronto, Asanka Jayasuriya has a strong educational foundation in technology.
Throughout his career, Asanka Jayasuriya has held various key roles in renowned organizations, showcasing his leadership and expertise.
With a history of involvement in prominent companies such as Amazon, Oracle, and SpaceX, Asanka Jayasuriya has proven his capabilities in the tech industry.
His experience ranges from software development and engineering to executive advisory positions, reflecting his versatile skill set and knowledge.
Asanka Jayasuriya's contributions as a former CTO, SVP Engineering, and Head of Engineering at different companies demonstrate his strategic thinking and technical proficiency.
Moreover, his engagements as an investor and advisor in multiple ventures highlight his interest in innovation and technology-driven businesses.
Asanka Jayasuriya's background encompasses a wide array of responsibilities and accomplishments, making him a reputable figure in cloud engineering and leadership.
Highlights
Incredibly proud of what the team at Terminal is building. Their plans for AI and computer vision are going to change the world of logistics.
Honored to be playing a small part in helping them achieve their goals alongside my #8VC teammates Jake Medwell and Wesley Friedman .
Oh and yes - they are hiring 😁!
#Crowdstrike released a pretty good Post Incident Review (PIR) about their outage last week.
The smoking gun in this PIR is the following corrective action they are going to implement:
“Implement a staggered deployment strategy for Rapid Response Content in which updates are gradually deployed to larger portions of the sensor base, starting with a canary deployment.”
For those not familiar with the concept gradual or incremental deployments allow you to slowly release features to production to see if anything goes wrong, and revert quickly if something does. The reason this strategy is critical in the cloud is that today’s systems are too complex to gain 100% confidence just by testing. So this strategy greatly mitigates your risk.
This is basic cloud software stuff. I expected my first year engineers to understand this concept within their first year. There are times when faults happen that are so hard , or complex edge cases - you have to accept that it may not have been preventable, because you never have seen that type of problem before. This was not that type of failure.
The fact that they didn’t have this process implemented and were rolling out to millions of endpoints without it is completely inexcusable and just irresponsible.
The impact of the outage demonstrated how important their software is, and how bad a mistake can be. I hope that beyond the PIR they look deep into their engineering culture and ask hard questions about why basic protective processes didn’t exist.
As a side note I love reading PIRs and encourage every technical leader to do so. At Amazon all PIRs were shared across the company and reading them was a huge learning opportunity.
#reliability #cloud
