Sanfaçon considered hosting Coveo’s own streaming service, but as troubling as the Amazon Kinesis outage was, he questioned whether Coveo could cost-effectively run a better messaging service with more uptime than AWS. Coveo is a search company, and the weeks around Black Friday are “go time” for many e-commerce customers. This outage didn’t affect Coveo’s main services but did affect their ability to onboard new organizations and record some types of events. “Just before black Friday, AWS had two major incidents with Kinesis, which is one of the services that using, but also one of the services that is the backbone of a lot of other services within AWS,” Sanfaçon noted. Sanfaçon shared another cloud problem that Coveo has grappled with: Keeping Coveo’s services functioning when Amazon’s services fail. Maintaining independence from cloud-specific services Sanfaçon mentioned Cloudability and CloudHealth as examples of tools you can use to control cloud spending. However, Sanfaçon notes a fledgling field of FinOps companies whose products help manage and optimize costs. and starts working on it.Ĭoveo already has someone working 75% of their day on cloud cost optimization. However, they have to make allowances for that developer who wakes up with inspiration at 2 a.m. Now Coveo turns off clusters or instances when no one is working, for example, 8 p.m. At the end of the month, you’re like, oh my god, that’s a lot of money.” But they can actually turn around and go into our AWS console and spin up a new machine that will cost the company 25 bucks an hour, and they leave that running for a month. “But when you have a company like ours with more than 200 developers,” Sanfaçon continued, “there are some policies in the company where they have to ask for authorization to buy a new phone, or a desk, or a chair. You pay for electricity, but then you use it as much as you want,” Marc Sanfaçon, senior vice president of technology and co-founder of Coveo, told me. Remember when people thought AWS was cheap? “When you actually have hardware that sits on-premises, you use it. Instead, I asked the people responsible for running some of the Internet’s most critical cloud-based services what problems they have faced, and how they solve or mitigate them.
And, good gosh, among all that complexity and a bunch of instances you are supposed to keep things stable and secure? And why is my Kubernetes config so dang long?
0 kommentar(er)
