text stringlengths 0 2.02k |
|---|
• Incident management platforms (e.g. FireHydrant, Incident.io) |
• Retroactive creation of runbooks after incidents occur |
• Importance of documentation and knowledge sharing within teams |
• Discussing the importance of testing backup and restoration systems |
• Exploring the trade-offs between pursuing high uptime and other priorities |
• Mentioning the value of curiosity and experimentation in software development |
• Discussing specific improvements to be made to the Changelog setup, including: |
• Incident management |
• Integrating Fastly logging with Grafana Cloud |
• Setting up Service Level Objectives (SLOs) for uptime and request failure rates |
• Noting the limitations and potential drawbacks of integrating Fastly logging, including the need to set up a proxy server to handle log authentication and potential DDOS issues |
• Mentioning alternative solutions, such as Honeycomb, that support direct integration with Fastly logging. |
• Integrating Honeycomb with existing tools and workflows |
• Discussing the benefits of using Honeycomb, including its ability to derive insights from complex systems |
• Analyzing the current deployment pipeline and identifying areas for improvement |
• Examining the impact of caching, dependencies, and cache invalidation on deployment times |
• Exploring the idea of creating a "smarter" pipeline that can adapt to different types of changes |
• Discussing the challenges of implementing such a pipeline, including the potential for complexity and brittleness |
• Mentioning the goal of reducing deployment times to 15 minutes or less |
• Discussing complexity of software development and the need to prioritize and simplify |
• Investigating and optimizing the 15-minute delay in a specific process |
• Considering a managed PostgreSQL database instead of hosting it internally |
• Moving media assets to an S3 object store instead of local disk |
• Addressing technical debt related to the assets uploader library in Elixir (Arc) |
• Importance of regularly discussing and prioritizing improvements to software quality and system efficiency |
• The app becomes effectively stateless, allowing for more flexibility and scalability. |
• The chaptering feature for mp3 files is discussed, with the goal of adding it to the platform to enhance user experience. |
• The lack of an ID3v2 library in Elixir is a major hurdle in implementing chaptering. |
• FFmpeg is used to add ID3 tags, but it overwrites local ID3 tags, making local chaptering difficult. |
• A possible solution is to pre-process mp3 files locally, adding chapters before uploading. |
• The feature of allowing clients to skip to specific topics is desirable, similar to YouTube video segments. |
• The ability to drag and drop files to automatically upload to S3 is also mentioned as a desirable feature. |
• Proposal to improve areas of discussion from previous episode |
• Plan to revisit discussion in 10 episodes |
• Reference to "kaizen" (continuous improvement philosophy) |
**Gerhard Lazu:** \[02:33\] So I really wanted to talk to you about this topic of Kaizen. Kaizen, for those that's the first time they hear this, is the concept of the art of self-improvement specifically. And that is really powerful, because it's the best way that you have to improve yourself, and to always think abou... |
**Adam Stacoviak:** Kaizen. I love it. |
**Jerod Santo:** Always Be Improving. ABI. |
**Adam Stacoviak:** ABI, yeah. Always Be Something. ABS. |
**Gerhard Lazu:** I'm pretty sure that means something else for others, ABS, but yes... |
**Adam Stacoviak:** Automatic Breaking System, that's what it refers to for me... |
**Gerhard Lazu:** The reason why I care so much about this is that having been part of Pivotal, this company which isn't anymore - it was acquired by VMware last year or two years ago - is that one of the core principles was to always be improving. "Be kind" was there as well. But always be improving was something that... |
\[04:05\] So having done it for 5, 6, 7 years, it's so deep-ingrained in me I cannot not do it. It's part of me. And I do it continuously. And I think the infrastructure setup that we've been rolling for some number of years has been an embodiment of that. Every year it has been improving. It was rooted in this princip... |
Now, one thing that we did in the past differently is that we improved, or at least we shared those improvements once per year. It was a yearly thing. And one of the ideas for the show was to do it more often, to improve more often. So we can improve in smaller steps, but also figure things out a lot, lot quicker, what... |
**Adam Stacoviak:** It works out at about every two-ish months essentially we get a response, a blip, a feedback loop, whereas before it was like once, or more recently twice in a year; if it's Kaizen every ten shows, then we get around four or five(ish) per year if you're shooting for 52 as a year. |
**Gerhard Lazu:** So I think in end of April, beginning of May we switched on the 2021 setup, and we had a show, we had an intro, we did a couple of things, episodes -- do you still remember which episode that was on Changelog, Adam? |
**Adam Stacoviak:** No, but I have the internet, and I will look it up... So give me a moment while I look it up. |
**Gerhard Lazu:** That is a good one. That was meant to be part of Ship It, but then some timelines got moved around, and that went on Changelog... And then the Ship It - we did the intro to the show. So that's how it happened. |
**Adam Stacoviak:** It was an interesting maneuver, a last-minute maneuver from us too, which - I'm not sure it matters to the listeners, but I think it was kind of... We had a plan, and then at the last minute we changed the first ten years of running down the field, so to speak. That was episode 441 on the Changelog'... |
**Gerhard Lazu:** I think that change made a lot of sense, and that change just led to a couple of other things... And now we're finally in the point to talk about the next improvement, so you don't have to wait another year; not only that, we're doing things slightly differently. We're going to share the things that w... |
So - Fastly. I would like to mention that, because Fastly, our partner - amazing CDN - had an outage a couple of weeks back. |
**Adam Stacoviak:** Unexpected, of course. |
**Jerod Santo:** Right after you said 100% uptime. |
**Gerhard Lazu:** Exactly. |
**Adam Stacoviak:** Exactly. \[laughter\] No, it was like a week after, wasn't it? That show shipped, and the very next week - Fastly outage. And it was a global outage, too. |
**Gerhard Lazu:** It was global. Half the internet broke. It was the biggest Fastly outage that I am aware of. So what that made me realize is that Fastly is great when it works. And when it doesn't, it doesn't affect just us, it affects everybody. BBC was down, and that's a big one, BBC being down. Emojis were down, o... |
**Jerod Santo:** Wait, wait, wait. Tell me more. How were emojis down for the whole internet? It doesn't make sense. |
**Gerhard Lazu:** Well, apparently, the assets that were served by AWS had something to do with it. I don't know exactly in which capacity, but AWS was serving certain emoji assets, and Fastly was part of that... And emojis stopped working for Slack, so I think in the Slack setup somewhere -- I mean, everybody uses Sla... |
**Jerod Santo:** \[08:05\] That makes more sense than "The emojis just stopped working globally", across the entire world of devices... But yeah, inside Slack. |
**Gerhard Lazu:** Sensational. It's news, it has to be sensational. \[laughter\] |
**Jerod Santo:** Well, most importantly, we were down, so most importantly to us... So the BBC being down - tragic; terrible for lots of people. But for us specifically, we were down, and that was the worst part about it, wasn't it? |
**Gerhard Lazu:** For us, yes. As for all the listeners. \[laughs\] Right. And interestingly, during this time, our origin, the backend to Fastly was up. It didn't have an issue. So this month I got a report, we were down for 21 minutes because of that. So 99.96% uptime. |
**Jerod Santo:** So you had a cutover though; you turned off Fastly basically, right? |
**Gerhard Lazu:** Yes. I jumped in, switched Fastly... Basically every routed traffic; so DNS updates, and Changelog.com would start resolving directly to the Linode host, talking to the Linode load balancer, node balancer, and Fastly was basically taken out of the picture. But because of how DNS is cached, it took a c... |
I was basically chilling, it was like a day off... It was a great one. I was in the garden, just chilling. Yeah, as you do, exactly... And then the phone started going off like crazy. That was really like "What?!" I got SMS messages, because we have multiple systems... When something is down, you really wanna know abou... |
**Jerod Santo:** Grafana, yeah. You didn't let me guess. I was gonna guess it. |
**Adam Stacoviak:** I thought you were saying you had a day off because of all the down time was giving you nothing to do. |
**Jerod Santo:** Grafana? Was it Grafana? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.