text stringlengths 0 1.8k |
|---|
[3417.32 --> 3420.00] He would enjoy and I would enjoy as well knowing about that. |
[3420.06 --> 3422.30] Yeah, we will both benefit from the answers. |
[3423.24 --> 3424.60] Well, this was fun, JSP. |
[3424.80 --> 3425.54] Thank you very much. |
[3425.68 --> 3426.24] See you next time. |
[3426.42 --> 3427.72] Yeah, thank you for the invitation. |
[3427.72 --> 3433.54] That's it for this episode of Ship It. |
[3433.82 --> 3435.20] Thank you for tuning in. |
[3435.42 --> 3438.36] We have a bunch of podcasts for developers at Changelog |
[3438.36 --> 3439.68] that you should check out. |
[3440.06 --> 3443.94] Subscribe to the master feed at changelog.com forward slash master |
[3443.94 --> 3446.26] to get everything we ship. |
[3446.68 --> 3450.70] I want to personally invite you to join your fellow changeloggers |
[3450.70 --> 3453.80] at changelog.com forward slash community. |
[3454.10 --> 3455.60] It's free to join and stay. |
[3455.60 --> 3459.16] Leaving, on the other hand, will cost you some happiness credits. |
[3459.64 --> 3461.18] Come hang with us on Slack. |
[3461.58 --> 3462.46] They're no imposters. |
[3462.88 --> 3464.06] Everyone is welcome. |
[3464.66 --> 3468.96] Huge thanks again to our partners Fastly, LaunchDarkly and Minote. |
[3469.30 --> 3473.98] Also, thanks to Breakmaster Cylinder for making all our awesome beats. |
[3474.44 --> 3475.64] That's it for this week. |
[3475.92 --> 3476.70] See you next week. |
[3476.70 --> 3506.68] See you next week. |
[3506.70 --> 3507.78] Bye. |
[3507.82 --> 3508.12] Bye. |
[3512.10 --> 3512.32] Bye. |
[3512.68 --> 3512.82] Bye. |
[3512.88 --> 3513.46] Bye. |
[3513.46 --> 3513.88] Bye. |
[3514.78 --> 3515.24] Bye. |
[3515.26 --> 3516.00] Bye. |
[3516.04 --> 3516.32] Bye. |
[3516.42 --> 3517.50] Bye. |
[3517.50 --> 3517.62] Bye. |
[3527.48 --> 3528.14] Bye. |
[3530.04 --> 3530.98] Bye. |
[3531.14 --> 3533.32] Bye. |
• Lars Wikman helped improve Changelog.com's codebase |
• He and Alex had differing approaches to improving performance |
• Lars worked on various projects for The Changelog, including email functionality and the meta-costs feature |
• Jerod has not implemented the meta-costs feature yet |
• Lars is deeply invested in the BEAM ecosystem (Erlang/Elixir) |
• His top favorite features of BEAM are concurrency/parallelism, resiliency, and dynamic typing |
• Shipping Elixir apps and their dependencies |
• Releases and packaging options for Elixir/Erlang |
• Docker and Docker Compose use cases and benefits |
• Database management with PostgreSQL, MySQL, SQLite, and Litestream |
• Stateful vs stateless systems and implications for deployment |
• The importance of simplicity and avoiding radical changes to existing software |
• Critique of Mnesia, a distributed database included with the BEAM ecosystem, citing scalability issues and conflict resolution problems |
• Use of SQLite as a caching solution for Elixir projects, leveraging standard tooling and compatibility with Ecto |
• Discussion of WhatsApp's use of Mnesia, employing it in a limited capacity due to concerns over consistency and performance |
• Evaluation of CockroachDB as a distributed database solution, highlighting its Postgres compatibility and scalability features |
• Concerns about using Kubernetes as an abstraction layer, arguing that developers should still be aware of underlying details such as Linux installations |
• Decision to use PostgreSQL instead of SQLite in a recent project due to the reliability and community support behind the former |
• Discussion of maintaining confidence in deployed software, including considerations for updates, CVEs, and backup strategies |
• Difficulty in taking small steps to improve systems as they become more complex |
• Importance of sticking with defaults and common paths for reliability and upgradability |
• Dangers of "chasing shiny" new technologies and frameworks without need or justification |
• Need to question the assumption that a product must be scalable, and to consider whether it's necessary |
• Value of writing retrospective posts to document lessons learned from past projects |
• Trade-offs between microservices and monolith architecture, and importance of knowing when to use each approach |
• Lars Wikman's skepticism towards using Kubernetes for small-scale systems |
• Gerhard Lazu's explanation of why Changelog chose to use Kubernetes (maturity, managed service offered by Linode) |
• Challenges with managing DNS updates and certificates in a Kubernetes environment |
• Discussion on using Ansible, Terraform, Concourse CI, and Docker Swarm before settling on Kubernetes |
• Benefits of using Kubernetes for complex systems with multiple concerns and integrations |
• Discussion around using proprietary cloud services for file serving |
• Comparison between using NGINX and Kubernetes for load balancing and infrastructure management |
• Difficulty in understanding the value proposition and benefits of using Kubernetes |
• Critique of Kubernetes as being overly complex, generalized, and "over-engineered" |
• Alternative approach to using a runtime environment like the BEAM (Erlang/Elixir) that provides high-availability and observability features out of the box |
• The discussion centers around the simplicity and complexity of Kubernetes |
• Gerhard Lazu defends Kubernetes as a complex but simple system with a clear interface and API |
• He compares it to other deployment tools like Chef and Ansible, stating that Kubernetes is a more comprehensive solution |
• Lars Wikman shares his experience with Kubernetes and notes its ability to simplify operations, but also paves over details |
• The conversation touches on the trade-off between simplicity and explicitness, with Gerhard arguing for a more declarative approach in certain situations |
• Lars likens Kubernetes to Electron, suggesting that it makes operations simpler but obscures underlying complexities |
• Both discussants agree that abstraction layers can be beneficial, but also highlight their potential drawbacks when applied incorrectly. |
**Gerhard Lazu:** I'd like to start with a story. I know that you've been helping Changelog.com, the codebase, in different ways... The thing which I remember is that our response latency went down; you did some tweaks... Is that right, or am I confusing you with Alex? |
**Lars Wikman:** I think Alex gets the credit on that... |
**Gerhard Lazu:** I definitely know he improved the N+1 queries, that's for sure... |
**Lars Wikman:** Yeah. I even caused some of those... |
**Gerhard Lazu:** Okay, okay... So you're the opposite of Alex. |
**Lars Wikman:** Yes, exactly. I'm here to create opportunities for performance improvements. |
**Gerhard Lazu:** I see. So that's the way it goes... Okay. So you're making it worse and he's making it better... The difference is like it's zero, right? Okay, so we're not going anywhere. |
**Lars Wikman:** \[04:04\] It's very important to have a stable codebase, and a very stable operation... \[laughs\] |
**Gerhard Lazu:** It is. |
**Lars Wikman:** Some of the work I've done with The Changelog has been on a few things that haven't been released, and a few things that -- basically, housekeeping around how emails are sent out, and to whom. I think and I hope that there will be some more stuff done with the meta-costs feature I made; I had the oppor... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.