DevOps & SRE notes – Telegram
DevOps & SRE notes
12K subscribers
42 photos
19 files
2.5K links
Helpful articles and tools for DevOps&SRE

WhatsApp: https://whatsapp.com/channel/0029Vb79nmmHVvTUnc4tfp2F

For paid consultation (RU/EN), contact: @tutunak


All ways to support https://telegra.ph/How-support-the-channel-02-19
Download Telegram
Have you ever heard that company migrate from microservice architecture to monolith?
Moving our service to a monolith reduced our infrastructure cost by over 90%. It also increased our scaling capabilities. Today, we’re able to handle thousands of streams and we still have capacity to scale the service even further. Moving the solution to Amazon EC2 and Amazon ECS also allowed us to use the Amazon EC2 compute saving plans that will help drive costs down even further.
https://www.primevideotech.com/video-streaming/scaling-up-the-prime-video-audio-video-monitoring-service-and-reducing-costs-by-90
In this post, the author explores various load balancing algorithms, including round robin, weighted round robin, dynamic weighted round robin, and least connections. The simulations demonstrate how these algorithms perform in different scenarios, highlighting their strengths and weaknesses. Round robin performs well in terms of median latency but struggles with higher percentiles. Least connections offer a good balance between simplicity and performance but may not be optimal in terms of latency. The PEWMA algorithm, which combines techniques from dynamic weighted round robin and least connections, shows significant improvements across all latency percentiles but has additional complexity and may not handle dropped requests as well as least connections. Ultimately, the choice of load balancing algorithm depends on the specific requirements of a workload and the performance characteristics that need to be optimized.

https://samwho.dev/load-balancing/
👍1
Adrien "ZeratoR" Nougaret's annual charity event, Zevent, returned this year with a new addition called Zevent Place. Inspired by Reddit's r/place, Zevent Place is a collaborative canvas where donors can draw pixels based on the amount they donate. Developers William Traoré and Alexandre Moghrabi created the platform with several features, such as Pixel Upgrade system and real-time updates, to protect community creations and enhance user experience.

The team utilized various technologies like GraphQL, NestJS, Redis, and MinIO, and managed to handle massive amounts of updates while maintaining a low CPU and bandwidth footprint. Although there were challenges, such as unexpected rate limit errors with Cloudflare, the event achieved 98.4% uptime, with the downtime being addressed and resolved promptly.

Overall, Zevent Place was a successful project, and valuable lessons were learned throughout its development and implementation.

https://medium.com/@alexmogfr/zevent-place-how-we-handled-100k-ccu-on-a-real-time-collective-canvas-71d3d346e0ab
Rhel compatible distribution in danger. RedHat change their policy and licenses agreements
https://www.jeffgeerling.com/blog/2023/dear-red-hat-are-you-dumb
SRE Report 2023 Catchpoint.pdf
16.2 MB
Now in its fifth year, The SRE Report has become the trusted source of trends and insights for reliability-as-a-feature practices. This year in partnership with Blameless, the report contains special contributions from Adrian Cockcroft and Steve McGhee and highlights findings from a global community of reliability practitioners, including SREs, managers, architects, and executives. As ever, we found some familiar trends and some thought-provoking anti-patterns.

Key findings include:

Organizations who operate with a “just culture” are 500% more likely to be Elite performing organizations. ‍
Elite-performing organizations are 260% more likely to substantially focus on Customer Experience reliability versus Low-performing organizations.
Organizations (59%) say that maintaining innovation velocity occasionally or often impacts employee productivity or morale – 14% unsure.
Organizations (59%) say tool sprawl is a non-existent or minor problem – challenges other research which simply equates tool sprawl to, ‘how many tools are in the stack’.