HackerTrans
TopNewTrendsCommentsPastAskShowJobs

misoukrane

no profile record

Submissions

[untitled]

1 points·by misoukrane·2 anni fa·0 comments

[untitled]

1 points·by misoukrane·2 anni fa·0 comments

[untitled]

1 points·by misoukrane·2 anni fa·0 comments

"14 Years of Go" by Rob Pike

codereliant.io
82 points·by misoukrane·2 anni fa·69 comments

SRE Interview Prep Plan (Week 5)

codereliant.io
4 points·by misoukrane·2 anni fa·0 comments

The System Resiliency Pyramid

codereliant.io
1 points·by misoukrane·2 anni fa·0 comments

Legacy CLIs No More

codereliant.io
5 points·by misoukrane·2 anni fa·2 comments

Why Distributed Systems Fail?

codereliant.io
3 points·by misoukrane·2 anni fa·4 comments

SRE Predictions for 2024

codereliant.io
2 points·by misoukrane·2 anni fa·1 comments

Making Software Reliable: The Importance of Testability

codereliant.io
41 points·by misoukrane·3 anni fa·23 comments

GitOps Guide: ArgoCD vs. Flux

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

SRE Interview Prep Plan (Week 4)

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

On Error Budgets

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

SRE Confessions

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

Learning From Google SRE Team (part-2)

codereliant.io
4 points·by misoukrane·3 anni fa·0 comments

Learning from Google SRE Team

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

Battle of the HTTP/Lang Frameworks

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

Load Shedding for High Traffic Systems

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

SRE Interview Prep Plan (Week 3)

codereliant.io
3 points·by misoukrane·3 anni fa·0 comments

Battle of the Frameworks: Benchmarking High-Performance HTTP Libraries

codereliant.io
2 points·by misoukrane·3 anni fa·0 comments

comments

misoukrane
·2 anni fa·discuss
Finally, looking forward to the benchmarks of many tools!
misoukrane
·2 anni fa·discuss
Oh I missed that - thanks for pointing out!
misoukrane
·2 anni fa·discuss
It got too big for one article. Part 2 of the article will be published next week.
misoukrane
·3 anni fa·discuss
In this post, we aim to analyze the technical factors that contributed to this tragedy, and discuss the engineering lessons we can learn from this incident.