explaingit

cheatsnake/backend-cheats

4,482Audience · developerComplexity · 1/5Setup · easy

TLDR

A visual reference guide covering the full backend development stack, networking, operating systems, databases, APIs, Docker, security, and deployment, with diagrams and source links for every topic.

Mindmap

mindmap
  root((backend-cheats))
    Networking
      HTTP and DNS
      VPN and proxies
      Browser loading
    Operating Systems
      Linux basics
      Processes threads
      Bash scripting
    Databases
      SQL and NoSQL
      Redis caching
      Schema design
    Delivery
      Docker
      CI/CD pipelines
      Load balancing
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Use as a structured roadmap to learn backend development from networking fundamentals to deployment pipelines.

USE CASE 2

Look up how HTTP, DNS, or TCP works with a visual diagram and a concise written explanation.

USE CASE 3

Reference Docker, load balancing, or message broker concepts before implementing them in a real project.

USE CASE 4

Study algorithm complexity, data structures, or database schema design with linked source material.

Tech stack

SQLDockerRedisBashLinux

Getting it running

Difficulty · easy Time to first run · 5min

In plain English

backend-cheats is a visual reference guide for people learning or working in backend development. The content is divided into chapters, each covering a distinct topic area. Within each topic, the format is consistent: a diagram, table, or image for quick visual understanding, a brief written summary with key terms linked to reference pages, and a hidden section of source links for readers who want to go deeper. The opening chapters cover networking. They explain how the internet is physically structured, what domain names and IP addresses are, how DNS translates between them, and how HTTP and TCP move data between computers. A section on browsers explains what happens when a page loads. Further entries cover VPN and proxy services, hosting options, and common network diagnostic tools. Operating system topics explain processes and threads, concurrency, how programs pass data to each other, and the basics of working in Linux. This includes using the command shell, managing packages, writing Bash scripts, handling users and permissions, scheduling background tasks, and reading system logs. Later chapters cover general computer science concepts such as data structures and algorithm complexity, then move into programming topics: object-oriented design, asynchronous code, and code quality. A database chapter addresses SQL databases, document stores, Redis, and how to design a data schema. API development covers REST, GraphQL, WebSockets, and remote procedure calls. The final sections deal with practical tooling and delivery: Docker, web servers, message brokers, security practices, testing approaches, deployment pipelines, monitoring, caching, load balancing, documentation, and architectural patterns. The repository is available in English and Russian. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Using the backend-cheats networking section as a guide, explain how a browser request travels from a URL to a rendered HTML page, step by step.
Prompt 2
I'm a frontend developer learning backend, create a 30-day study plan based on the topics in backend-cheats.
Prompt 3
Explain the difference between REST, GraphQL, and WebSockets as described in the backend-cheats API section, and tell me when to use each.
Prompt 4
Walk me through the Docker and deployment topics from backend-cheats and show me how to containerize a simple Python web app.
Prompt 5
Based on the backend-cheats database chapter, help me decide between SQL, a document store, and Redis for my use case.
Open on GitHub → Explain another repo

← cheatsnake on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.