#Linux

➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

#Network
#QA

➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

⚙️ #SystemDesign 📈📊📊

Data is cached everywhere, from the front end to the back end!
This diagram illustrates where we cache data in a typical architecture.
There are multiple layers along the flow :

1. Client apps: HTTP responses can be cached by the browser.
We request data over HTTP for the first time, and it is returned with an expiry policy in the HTTP header; we request data again, and the client app tries to retrieve the data from the browser cache first.

2. CDN: CDN caches static web resources. The clients can retrieve data from a CDN node nearby.
3. Load Balancer: The load Balancer can cache resources as well.

4. Messaging infra: Message brokers store messages on disk first, and then consumers retrieve them at their own pace.
Depending on the retention policy, the data is cached in Kafka clusters for a period of time.

5. Services: There are multiple layers of cache in a service. If the data is not cached in the CPU cache, the service will try to retrieve the data from memory. Sometimes the service has a second-level cache to store data on disk.

6. Distributed Cache: Distributed cache like Redis hold key-value pairs for multiple services in memory. It provides much better read/write performance than the database.

7. Full-text Search: we sometimes need to use full-text searches like Elastic Search for document search or log search. A copy of data is indexed in the search engine as well.

8. Database: Even in the database, we have different levels of caches:
WAL(Write-ahead Log): data is written to WAL first before building the B tree index

9. Bufferpool: A memory area allocated to cache query results
Materialized View: Pre-compute query results and store them in the database tables for better query performance

10. Transaction log: record all the transactions and database updates
Replication Log: used to record the replication state in a database cluster.

©️ From : ByteByteGo

➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

#Kubernetes

100 Kubernetes Errors &
Solutions
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

⭐️گروه تلگرامی⭐️

جهت بحث و گفتوگو های فنی :
👇👇👇👇👇
💎 @DevopsDocGp 💎

#AWS

AWS CLI cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

#Docker

➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

⭐️گروه تلگرامی⭐️

جهت بحث و گفتوگو های فنی :
👇👇👇👇👇
💎 @DevopsDocGp 💎

#Cloud
#Network

➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

#Jenkins

➖➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc

#Book
#Kubernetes

➖➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.iss.one/DevopsDocGP
Channel:
©️ https://t.iss.one/DevopsDoc