ِ

مهتم بالتقنية ونشر #المعرفة_الرقمية👨‍💻 @harmashcom

[ِ @tork57]

@yousef9911 تطبيق ختمة ، بدون إعلانات @KhatmahApp
ورد اليوم، الأذكار، مواقيت الصلاة،
وتفسير القرآن لو ضغطت على كل آية
أشوفه ممتاز جداً ومفيد👌
جزاهم الله عنا خير الجزاء

[ِ @tork57]

@HungerStation رقم الطلب 1653877952#

تم الطلب الساعة 2:11 مساءً
وصل الطلب الساعة 4 مساءً

توصيل الطلب ساعتين ؟!!!! @HungerStation

كم ياخذ معكم توصيل الطلب ؟
@Ninjaappksa @JahezCareKSA @Keetaglobal_ksa

[ِ @tork57]

@HungerStation - تأخير أكثر من اللازم
- مستلم الطلب في مكان بعيد جداً عن الموقع
- لا يمكن إلغاء الطلب
- وعدم الإلتزام بالوقت المحدد
- لا يوجد تعويض مكافئ للتأخير
- تأخير زمن التسليم كل مرة

[ِ @tork57]

@PlannerVisa أقرب موعد للإيطالية ؟

[ِ @tork57]

@qunaibet @DrHuzam أنا قمت بسداد المخالفات
ولدي ايصال السداد من نفس تطبيق أمانة الرياض
ولكن حتى بعد سدادها !!
لا زالت موجودة في التطبيقات المصرفية
مطلوب سدادها كذلك 😅
لا يوجد رقم للتواصل
واستقبال الشكاوى
ورفع المقترحات
والاعتراضات @Amanatalriyadh

[Vanshika @vanyaSile]

Redis stores data in RAM.

RAM gets wiped after a restart.

So... why doesn't Redis lose all your data? 🤔

[Sevalla @sevalla_hosting]

A good API should be easy to understand, hard to misuse, and simple to evolve. 🔌

Here are the core principles of strong API design:

1️⃣ Use clear resource names

Prefer nouns over actions:

/users
/orders
/products/12

2️⃣ Use HTTP methods correctly

🔍 GET - read data
➕ POST - create data
♻️ PUT - replace data
✏️ PATCH - update part of data
🗑️ DELETE - remove data

3️⃣ Keep endpoints consistent

Use the same naming style, casing, response structure, and error format across the entire API.

4️⃣ Return useful status codes

✅ 200 - OK
✅ 201 - Created
✅ 204 - No Content
⚠️ 400 - Bad Request
🔐 401 - Unauthorized
🔎 404 - Not Found
🧩 422 - Validation Error
💥 500 - Internal Server Error

5️⃣ Make errors helpful

Do not return only “Something went wrong.”

Include a clear message, error code, and details that help developers fix the request.

6️⃣ Design for real workloads

Use:

📄 Pagination for large lists
🔍 Filtering and sorting
🚦 Rate limiting
🛡️ Input validation
🔐 Authentication and authorization
📊 Logs, metrics, and tracing

7️⃣ Version carefully

Avoid breaking existing clients. Support backward compatibility and introduce new versions only when necessary.

A simple REST pattern:

GET /products - list products
GET /products/12 - get one product
POST /products - create a product
PATCH /products/12 - update a product
DELETE /products/12 - delete a product

The best APIs feel predictable.

Developers should be able to understand the next endpoint without constantly checking the documentation. 🚀

[kelvinlina𖤍💜✨ @cybergirl_io]

Best illustration 📌

[YourCloudDude | AWS & Python @yourclouddude]

PYTHON Beginner to ADV. checklist for you 🚀

[Ayaan 🐧 @twtayaan]

A visual guide to how containers really work 📦

[Artificial Intelligence @AIGuideHQ]

Latency vs Throughput vs Bandwidth

[Vishwanath Patil @patilvishi]

Evolution of Software Deployment

Deploying software used to be a stressful event.

Today, companies deploy hundreds even thousands of times without users noticing.

Here's how we got here.

1980s–1990s → Manual Deployment
Copy binaries and files directly to servers. Every deployment was a carefully planned event.
⬇️
1990s–2000s → FTP & Deployment Scripts
Teams started automating repetitive deployment steps with scripts.
⬇️
2000s → Continuous Integration (CI)
Automated builds and testing made releases faster and safer.
⬇️
2010s → Cloud & Infrastructure as Code
Infrastructure became programmable and environments became reproducible.
⬇️
Mid-2010s → Containers & Docker
Applications were packaged with their dependencies, making deployments consistent across environments.
⬇️
Late 2010s → Kubernetes & Container Orchestration
Deployments became automated, scalable, self-healing, and easier to manage across clusters.
⬇️
2020s → GitOps & Progressive Delivery
Git became the source of truth. Canary releases, blue-green deployments, and feature flags reduced deployment risk.
⬇️
Today & Beyond → AI-Assisted Operations
AI is increasingly helping analyze failures, detect anomalies, recommend fixes, and automate parts of deployment operations.

Every generation solved a different challenge
Manual → Get software onto a server
Scripts → Automate repetitive steps
CI/CD → Ship faster and more reliably
IaC → Make infrastructure reproducible
Containers → Run consistently anywhere
Kubernetes → Orchestrate applications at scale
GitOps → Make deployments declarative and auditable
AI-Assisted Ops → Detect, diagnose, and respond faster

The biggest shift?
Deployment went from being an event to becoming a continuous process.

We moved from:
"Don't deploy on Friday."
to:
"Deploy anytime with the right automation, observability, and rollback strategy."

How are you deploying to production today?
Manual , CI/CD , Docker , Kubernetes , GitOps and Serverless

#DevOps #Deployment #CICD #Docker #Kubernetes #GitOps #CloudComputing #SoftwareEngineering #SRE #PlatformEngineering #Developers

[Python Crafted @PythonCrafted]

Master Opensource LLM Model with this single post and crack you next interview !!

[Artificial Intelligence @AIGuideHQ]

Public Cloud vs Private Cloud vs Hybrid Cloud.

[𝐇𝐚𝐦𝐳𝐚 | Networking Guy @Hamzaonchain]

DATA CENTER 3-LAYER ARCHITECTURE

As a network grows, connecting every device directly becomes difficult to manage. That's why many enterprise networks use a three-layer design: Access, Distribution, and Core.

The Access Layer is where users and devices connect to the network. This includes PCs, servers, IP phones, wireless access points, and security cameras. Access switches provide these devices with network connectivity and often power them using PoE.

The Distribution Layer sits above the access layer and acts like a traffic manager. It connects multiple access switches together, performs inter-VLAN routing so different departments can communicate, applies security policies, and helps balance network traffic efficiently.

At the top is the Core Layer, the backbone of the network. Its main job is to move large amounts of data between different parts of the network as quickly and reliably as possible. Core switches are built for speed, redundancy, and high availability, ensuring the network stays online even if a link or device fails.

You can think of it like a road system:

• Access Layer = Local streets where people enter the network.

• Distribution Layer = Major roads that organize and direct traffic.

• Core Layer = The highway that moves traffic across the network at very high speed.

This layered design makes enterprise networks easier to scale, troubleshoot, secure, and maintain as they grow from a few dozen devices to thousands.

[Tech Fusionist | Kushal Gangil @techyoutbe]

Master Linux, One Command at a Time! 🚀

These essential commands will make you unstoppable in the terminal. Let’s dive in! 🧵

Bookmark & share with your network!

[Tech Fusionist | Kushal Gangil @techyoutbe]

If I had to learn LLM Engineering again, this is the roadmap I'd follow.

No fluff. No random tutorials.

Just a structured path from embeddings and transformers to RAG, agents, alignment, and production deployment.

[Dhanian 🗯️ @e_opore]

Docker Cheatsheet (Beginner to Advanced)

Docker Basics

→ docker --version → Check Docker version
→ docker info → Display Docker system information
→ docker help → Show Docker help menu
→ docker version → Display client and server versions

Images

→ docker pull → Download an image
→ docker images → List local images
→ docker build → Build image from Dockerfile
→ docker tag → Tag an image
→ docker push → Push image to registry
→ docker rmi → Remove an image
→ docker image prune → Remove unused images

Containers

→ docker run → Create and start a container
→ docker ps → List running containers
→ docker ps -a → List all containers
→ docker start → Start a stopped container
→ docker stop → Stop a running container
→ docker restart → Restart a container
→ docker rm → Remove a container
→ docker rename → Rename a container
→ docker exec → Execute command inside container
→ docker attach → Attach to a running container

Logs & Monitoring

→ docker logs → View container logs
→ docker stats → Monitor resource usage
→ docker top → Show running processes
→ docker inspect → View detailed container information
→ docker events → Stream Docker events

Volumes

→ docker volume create → Create a volume
→ docker volume ls → List volumes
→ docker volume inspect → View volume details
→ docker volume rm → Remove a volume
→ docker volume prune → Remove unused volumes

Networks

→ docker network ls → List networks
→ docker network create → Create network
→ docker network inspect → Inspect network
→ docker network connect → Connect container to network
→ docker network disconnect → Disconnect container
→ docker network rm → Remove network

Docker Compose

→ docker compose up → Start services
→ docker compose down → Stop and remove services
→ docker compose ps → List services
→ docker compose logs → View service logs
→ docker compose build → Build services
→ docker compose restart → Restart services
→ docker compose exec → Run command in service

Dockerfile Instructions

→ FROM → Base image
→ WORKDIR → Set working directory
→ COPY → Copy files into image
→ ADD → Copy files and URLs
→ RUN → Execute command during build
→ CMD → Default container command
→ ENTRYPOINT → Main executable
→ ENV → Set environment variables
→ EXPOSE → Document exposed port
→ VOLUME → Create mount point
→ USER → Set execution user
→ LABEL → Add image metadata

Registry

→ docker login → Authenticate to registry
→ docker logout → Sign out of registry
→ docker search → Search Docker Hub
→ docker pull → Download image
→ docker push → Upload image

Cleanup

→ docker system df → Show Docker disk usage
→ docker system prune → Remove unused resources
→ docker container prune → Remove stopped containers
→ docker image prune → Remove dangling images
→ docker volume prune → Remove unused volumes
→ docker network prune → Remove unused networks

Advanced

→ docker save → Export image to archive
→ docker load → Import image archive
→ docker export → Export container filesystem
→ docker import → Create image from archive
→ docker cp → Copy files between host and container
→ docker diff → Show container filesystem changes
→ docker history → Show image layer history

Best Practices

→ Use lightweight base images → Reduce image size
→ Use multi-stage builds → Optimize production images
→ Keep containers stateless → Improve scalability
→ Pin image versions → Ensure reproducible builds
→ Scan images regularly → Improve security
→ Minimize image layers → Faster builds and deployments

📘 Grab Docker Ebook:
https://t.co/DLllv30suF

[الأكاديمية السعودية الرقمية @SdaAcademy]

المقاعد محدودة، والتسجيل مستمر.

طوّر مهارات تصنع المستقبل، واستعد لفرص مهنية تواكب احتياجات سوق العمل.

سجّل الآن:
https://t.co/VAAVg2H7Fb

#الأكاديمية_السعودية_الرقمية