#Linux ⚠️

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

#Terraform

Terraform cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

Devops T-Shooting
➖➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

#Helm

Helm cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

#AWS

AWS cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

⚙️ #SystemDesign 📈📊📊

🤔How Do Companies Ship Code to Production?

Here are 11 steps from planning to production:
➡️
1) The Product Owner starts the entire process by creating user stories in a tool like Jira.

2) The Developer Team performs Sprint Planning activity and adds the user stories to the sprint.

3) Developers work on the assigned stories. Once a story is finished, they commit the code to Git and push it to GitHub.

4) Jenkins builds and runs the code through testing and quality check tools such as JUnit, Jacoco, and SonarQube.

5) If the build is successful, it is stored in the artifactory such as JFrog. Jenkins also deploys the build to the Dev Environment via Docker.

6) Next up, the feature gets deployed to the QA environment.
Since multiple teams may be working on the same code base, multiple QA environments will be created.

7) The QA team uses a particular QA environment and runs multiple test types such as QA, regression, and performance.

8) Once the QA verification is complete, features are deployed to the UAT (User Acceptance Testing) environment.

9) UAT testing verifies whether the feature satisfies the user's requirements.

10) Once the UAT testing is successful, the builds become release candidates. They are deployed to the production environment based on a specific schedule.

11) The SRE team uses tools like ELK and Prometheus to monitor the production environment and handle alerts in case of issues.


©️ From : ByteByteGo

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

#Docker

Docker cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

#Linux

Linux cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

#Kubernetes

Kubernetes cheat sheet
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc

⚙️ #SystemDesign 📈📊📊

An HTTP server cannot automatically initiate a connection to a browser. As a result, the web browser is the initiator. What should we do next to get real-time updates from the HTTP server?

Both the web browser and the HTTP server could be responsible for this task.

🔴Web browsers do the heavy lifting: short polling or long polling. With short polling, the browser will retry until it gets the latest data. With long polling, the HTTP server doesn't return results until new data has arrived.
🔴HTTP server and web browser cooperate: WebSocket or SSE (server-sent event). In both cases, the HTTP server could directly send the latest data to the browser after the connection is established. The difference is that SSE is uni-directional, so the browser cannot send a new request to the server, while WebSocket is fully-duplex, so the browser can keep sending new requests.

➡️Over to you: of the four solutions (long polling, short polling, SSE, WebSocket), which ones are commonly used, and for what use cases?


©️ From : ByteByteGo

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

#AWS
#QA

AWS question & answer
➖➖➖➖➖➖➖➖➖➖➖➖
Group:
©️ https://t.me/DevopsDocGP
Channel:
©️ https://t.me/DevopsDoc