List of videos

Read the abstract ➤ https://www.conf42.com/Golang_2024_Prabesh_Thapa_optimizing_performance_security Other sessions at this event ➤ https://www.conf42.com/golang2024 Support our mission ➤ https://www.conf42.com/support Join Discord ➤ https://discord.gg/DnyHgrC7jC Chapters 0:00 intro 0:20 preamble 0:45 whoami 0:59 things we want our api to be 1:19 secure - authentication / authorization 4:26 validate unputs 4:55 log user activity (audit trails) 5:52 use appropriate response 6:37 password management 8:16 use config file vs env vars 9:31 mask sensitive data 10:04 implement rate limiting 12:01 secure communication 12:33 patch your dependencies 13:06 fast - use optimized database queries 14:24 implement caching 15:24 pagination 16:24 break into smaller service 17:26 robust 17:36 fail early fail fast 18:31 use appropriate status code 19:52 don't just check errors, handle them gracefully 20:58 context passing 22:32 acid compliance 23:48 context passing 23:52 use structured logs 24:19 implement health checks 25:33 handle retries gracefully 27:04 expose metrics 27:53 version for maintainability 28:38 conclusion 28:58 thank you

Read the abstract ➤ https://www.conf42.com/Golang_2024_Sandeep_Bhat_custom_load_balancer_envoy Other sessions at this event ➤ https://www.conf42.com/golang2024 Support our mission ➤ https://www.conf42.com/support Join Discord ➤ https://discord.gg/DnyHgrC7jC Chapters 0:00 intro 0:20 preamble 0:29 sandeep bhat 1:02 what is load balancing 3:33 cloud native options 4:20 envoy 4:56 features of envoy 5:34 key components of envoy 7:49 requirements of custom load balancer 8:45 components of envoy based load balancer 10:31 envoy - service 12:09 snippet - controller 13:54 packaging - cloud init 14:48 sample - cloud init 15:19 requirements of cusotm load balancer 15:40 components of envoy based load balancer 16:04 cost comparison 17:22 demo 19:46 thank you

Read the abstract ➤ https://www.conf42.com/Golang_2024_Eugene_Khabarov_build_enough_bazel Other sessions at this event ➤ https://www.conf42.com/golang2024 Support our mission ➤ https://www.conf42.com/support Join Discord ➤ https://discord.gg/DnyHgrC7jC Chapters 0:00 intro 0:20 preamble 0:30 agenda 0:39 build and dependencies - what is "go build"? 1:01 do we have all of the *.go files from the beginning? 1:25 dependencies: part I 1:33 where do we run our build? 1:45 dependencies: part II 2:04 publishing 2:32 dependencies: part III 2:45 what is the dependency, btw? 2:55 how do we control our dependencies? 3:31 what else should we consider during the build process? 4:00 the output of the build process aka artifacts 4:16 why "go build" isn't enough? 4:25 problem scope 5:07 bazel 5:54 build & cache 6:40 hermeticity & sandboxing 7:45 hello world generator 8:25 and with bazel 8:59 hellow world generator: bazelified 9:39 starlark 9:53 workspace 10:32 go/build.bazel 11:16 build & run 11:44 demo: microservices, kubernetes and tilt 13:30 labels 14:37 should we write build files manually? 15:19 what else? 15:21 bazel query 15:29 dependency graph 15:43 extensibility 16:12 more info on bazel 16:21 thank you

Read the abstract ➤ https://www.conf42.com/Golang_2024_Haseeb_Majid_using_nix_reproducible Other sessions at this event ➤ https://www.conf42.com/golang2024 Support our mission ➤ https://www.conf42.com/support Join Discord ➤ https://discord.gg/DnyHgrC7jC Chapters 0:00 intro 0:20 preamble 0:48 who is this for? 2:12 what is nix? 3:52 declarative 5:21 what is the problem? 6:50 summary 8:11 golang 9:07 tools.go 10:30 creative our first dev environment 10:40 flake.nix 13:02 summary 13:31 direnv 14:07 usage 15:14 remote environments 15:44 pre-commit 17:22 summary 17:52 how does nix work? 19:46 evaluation 20:26 derivations 21:41 advantages 25:22 nix flakes 26:14 flake.nix 26:26 flake.lock 27:35 ci 27:50 gitlab ci 29:15 ci logs 29:41 why not docker? 31:06 further 31:13 slides, links, resources 31:32 reference & thanks

Conf42 Incident Management starts here! Schedule, Lineup & RSVP: https://www.conf42.com/im2022 Join Discord to interact: https://discord.gg/DnyHgrC7jC 0:00 sponsored segment 1:00 intro, sponsors & partners keynotes 1:59 Ryan McDonald 2:26 Vanessa Huerta Granda 3:11 Nick Mason & Emily Arnott 4:04 Ankit Jain 4:45 Jeff Nickoloff 5:22 Lisa Karlin Curtis culture 5:43 Hila Fish 6:30 Mandi Walls 7:05 Amir Shaked tools 7:30 Ricardo Castro 8:19 Valera Bronshtein deep dive 9:01 Chris Nesbitt-Smith 9:29 Hari Krishnan 10:02 Nishant Roy 10:42 Eran Levy lessons learned 11:21 Brian Contos 12:17 Kurt Andersen 13:05 panel Discussion teaser: Nora Jones, Erin McKeown & Charity Majors 13:25 Thank you, Join our Discord to interact! https://discord.gg/DnyHgrC7jC

Nora Jones, Erin McKeown & Charity Majors will discuss the Incident Management practices in their respective organizations. Other talks at this conference 🚀🪐 https://www.conf42.com/im2022

Organizations are focusing on incidents more than ever but failing to leverage them to their full potential. But by framing incidents and post-incident reviews as customer empathy-building opportunities, we can facilitate more creative technical problem-solving, unlock improvements to your response process, and enable organizational agility that otherwise might have gone unnoticed. This talk will deliver actionable methods to increase customer empathy before, during, and after an incident. Other talks at this conference 🚀🪐 https://www.conf42.com/im2022 — 0:00 Intro 1:40 Talk

One more step in Learning from Incidents: Sharing incident findings effectively Oftentimes post-incident activities involve a post-mortem meeting and document. These 2 vary in quality, from focusing only on a single root cause, maybe a 5-why’s, or on the bright side, a thorough investigation that takes into account multiple points of view. Regardless, once the meeting is complete, the output usually ends up in a document hidden in a drive that no-one ever opens and the knowledge that was discovered during the postmortem stays only with those who attended the meeting. If learning from incidents allows us to turn outages into opportunities, how can we make those learnings reach the most people? We do this by carefully and thoughtfully sharing our findings. By sharing our findings we allow for more equitable learning (account for people with conflicts or illnesses who couldn’t attend the review meeting), can get buy-in for next steps, get people in the org to have a more well-rounded knowledge of how things work. This talk is meant for anyone who is involved in incidents in any way: responders, subject matter experts, impacted users, and facilitators but mostly for technologists who want to make the most out of their incidents through learning! Throughout this talk I will give an overview of why sharing matters and go deep through the different ways that we can share incident learnings depending on your needs and audiences as well as provide examples with the hope that folks are able to start applying these forms of communication in their own orgs. Furthermore, I want folks who watch this talk to leave with a sense that change can happen and that we aren’t meant to keep repeating the same problems over and over again. Other talks at this conference 🚀🪐 https://www.conf42.com/im2022 — 0:00 Intro 0:39 Talk

When something goes wrong, it can be tempting to gather as many people as you can to fix it. Each person can contribute tremendous value through diverse viewpoints, but too many people can overcrowd your response, leading to miscommunication, redundant work, and much more. This talk will teach you to avoid overcrowding incidents through smarter escalation policies, role-based tasks to organize efforts, and more efficient communication. A lean, focused team of relevant players can achieve much more than a bloated, confused one. Only then will you start to reduce the burden for your on-call team and keep customers happy. Blameless is drawing! Participate in a raffle to win Beats Solo Wireless: https://info.blameless.com/raffle-conf42-incident-management Other talks at this conference 🚀🪐 https://www.conf42.com/im2022 — 0:00 Intro 0:39 Talk