AF

[Ivan Velichko @iximiuz]

How Container Filesystem Works 🧐

Building a Docker-like container from scratch using only standard Linux commands (unshare, mount, pivot_root, etc.) is a great way to understand exactly what a container runtime like runc does under the hood to turn a container image into a fully-fledged rootfs.

Hands-on: https://t.co/PC7c9Zy1SJ

[AF @afrank]

https://t.co/KvTf18RMIA

[AF @afrank]

https://t.co/3UmqUy2ObS

[AF @afrank]

https://t.co/MolWxJ7TXz

[AF @afrank]

https://t.co/gnKuo1Sfdy

[AF @afrank]

https://t.co/PqsMNdyrWY

[AF @afrank]

https://t.co/JyxpVNCYXD

[AF @afrank]

https://t.co/y3ClbFkNsu

[AF @afrank]

https://t.co/L67xRQED4N

[Sahn Lam @sahnlam]

SSH Under the Hood

[AF @afrank]

https://t.co/H3b54O4Epn

[AF @afrank]

https://t.co/EtjUu2ZEi0

[TRÄW🤟 @thatstraw]

Linux cron job essentials

[AF @afrank]

https://t.co/mJlpZF66lX

[AF @afrank]

Bresenham's Circle Drawing Algorithm - https://t.co/lKJydt0jE9

[AF @afrank]

https://t.co/a6Tj0LE0hO

[AF @afrank]

https://t.co/jvapiNbgQ1

[AF @afrank]

https://t.co/NaK9zWaXxP

[Bytebytego @bytebytego]

Key Concepts to Understand Database Sharding.

In this concise and visually engaging resource, we break down the key concepts of database partitioning, explaining both vertical and horizontal strategies.

1. Range-Based Sharding: Splitting your data into distinct ranges. Think of it as organizing your books by genre on separate shelves.

2. Key-Based Sharding (with a dash of %3 hash): Imagine each piece of data having a unique key, and we distribute them based on a specific rule. It's like sorting your playing cards by suit and number.

3. Directory-Based Sharding: A directory, like a phone book, helps you quickly find the information you need. Similarly, this technique uses a directory to route data efficiently.

Over to you: What are some other ways to scale a database?

–
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/FIzCeaWsZV

[Bytebytego @bytebytego]

What does API gateway do?

The diagram below shows the detail.

Step 1 - The client sends an HTTP request to the API gateway.

Step 2 - The API gateway parses and validates the attributes in the HTTP request.

Step 3 - The API gateway performs allow-list/deny-list checks.

Step 4 - The API gateway talks to an identity provider for authentication and authorization.

Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected.

Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching.

Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices.

Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway.

Over to you: 1) What’s the difference between a load balancer and an API gateway?
2) Do we need to use different API gateways for PC, mobile and browser separately?

–
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/FIzCeaWsZV