int128 / README.md

Last active April 12, 2025 13:02

Example of Envoy TCP Proxy

This page has been moved to https://github.com/int128/hello-envoy

Envoy TCP Proxy

This is an example of Envoy TCP Proxy from localhost:10000 to www.google.com:80. See also https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/listeners/tcp_proxy.

To run a proxy:

vdmitriyev / knowledgebase-gist.md

Last active March 15, 2025 12:09

random / temporary links for reading / reviewing

📑 ➡️ ✅ Articles and materials that are DONE / READ

💬 materials below were revised and remained interesting / useful
sort order -> latest to oldest

ejlp12 / eks_best_practice.md

Last active March 10, 2025 12:29

EKS Best Practice

Please check https://aws.github.io/aws-eks-best-practices/ for more comprehensive EKS best practice!

Architecture

Think about multi-tenancy, isolation for different environment or different workload
- Isolation at account level using AWS organization
- Isolation at the network layer ie. different VPC & different cluster
- Use different Nodes Group (Node pool) for different purpose/category e.g. create dedicated node groups for Operational tools such as CI/CD tool, Monitoring tool, Centralize logging system.
- Separate namespace for different workload

Reliability | Principles

vegard / kernel-dev.md

Last active April 1, 2025 19:37

Getting started with Linux kernel development

Prerequisites

The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.

It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.

Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.

craigtp / AdvancedDistributedSystemDesignCourseNotes.md

Created May 1, 2020 19:38

Notes on Udi Dahan's Advanced Distributed System Design Course

Advanced Distributed System Design Course - Udi Dahan

Notes by Craig Phillips

Fallacies of Distributed Computing

There are 11 fallacies of Distributed Computing:
1. The network is reliable
2. Latency isn’t a problem
3. Bandwidth isn’t a problem
4. The network is secure

The topology won’t change

amad / The_Well-Architected_Framework_Checklist.md

Last active January 6, 2024 04:07

AWS Well-Architected Framework Checklist

The Well-Architected Framework Checklist

This is the set of questions presented on The Well-Architected Framework whitepaper designed to evaluate how well your architecture is aligned with AWS best practices.

Security Pillar

Data Protection

How are you encrypting and protecting your data at rest?

somahargitai / ThingsMakeMeMad.MD

Last active October 26, 2024 19:36

My universal IT complainer surface

I just complain here

This is a complainer surface to show the world the dark side of my real-life developer experience

content

Things software engineers say about work

neomantra / High_Performance_Redis.md

Last active January 14, 2025 16:07

Notes on running Redis with HPC techniques

High Performance Redis

In response to this brief blog entry, @antirez tweeted for some documentation on high-performance techniques for Redis. What I present here are general high-performance computing (HPC) techniques. The examples are oriented to Redis. but they work well for any program designed to be single- or worker-threaded and asynchronous (e.g. uses epoll).

The motivation for using these techniques is to maximize performance of our system and services. By isolating work, controlling memory, and other tuning, you can achieve significant reduction in latency and increase in throughput.

My perspective comes from the microcosm of my own bare-metal (vs VM), on-premises deployment. It might not be suitable for all scenarios, especially cloud deployments, as I have little experience with HPC there. After some discussion, maybe this can be adapted as [redis.io documentation](https://redis.io/do