roadmap.sh: Backend Developer

What the roadmap shows

The backend roadmap lays out the territory between writing an endpoint and running a reliable service. The main areas include:

• Fundamentals: how the internet works, choosing a language (such as JavaScript with Node.js, Python, Java, Go, C#, PHP or Ruby) and version control with Git.
• Databases: relational databases (PostgreSQL is commonly recommended), NoSQL options, ORMs, indexing, transactions, ACID, normalisation and replication.
• APIs: REST, JSON, GraphQL, gRPC, authentication (JWT, OAuth, sessions) and API security.
• Caching at the server, client and CDN level, and web servers.
• Testing, CI/CD and security basics.
• Architecture and scaling: containers, message brokers, design patterns, observability, and scaling approaches.

Nodes are marked to show which are recommended, which are alternatives, and which are optional, and clicking a node opens a short explanation with links. There is a simpler beginner version, a projects section with practice ideas, and an AI tutor for questions.

How popular it is

roadmap.sh reports more than 3.2 million registered users and a Discord community of about 51,000 (September 2026). Its GitHub repository, developer-roadmap, had about 368k stars, making it one of the most starred projects on GitHub.

What it clarifies

Backend work has a much wider surface than beginners expect, and most of it is invisible from the outside. Seeing caching, message queues, observability and deployment on the same map as writing an endpoint is a useful correction to the idea that backend means writing endpoints.

How to use it without drowning

• Start with the beginner version if you are new. The full map is intimidating.
• Pick one language and one relational database and stick with them for months. Depth beats breadth.
• Take one node at a time. Learn it, then build something that uses it, such as adding caching or authentication to your own API.
• Use the progress tracking to mark what you know, which makes gaps visible.
• Do the projects. A roadmap is a map, not a course; the learning comes from building.

Where it falls short

The roadmap tells you what exists, not how deeply to learn it or in what order within a node. The linked resources vary in quality. It can also make everything look equally urgent, which it is not: a junior backend developer needs a language, SQL, HTTP, REST APIs, authentication, Git and testing far more than service meshes.

Common questions

Is it free? Yes. The roadmaps are free, with an optional account for progress tracking.

Do I need to learn everything on it to get a job? No. Junior roles expect the fundamentals done well. The rest comes with experience.

Which language should I pick? The one used by jobs you want, or the one you know. JavaScript (Node.js), Python, Java, C# and Go are all solid choices.

Best for: developers moving from frontend into full stack, and self-taught backend engineers checking for gaps.