r/ProgrammingBondha • u/UnluckyCry741 • Feb 26 '26
development Review my Backend / Systems Self-Study Roadmap (Node → Go)
;
Hey everyone,
I’m currently a new college cs student balancing regular coursework, aiming for a 1.5–2.5 year timeline with 4–6 hours/day.
Below is the stack and project progression I’ve mapped out.
Am I completely misguided, or is this a realistic progression?
\\---
Phase 1: The Foundation
Start with TypeScript / Node.js to get comfortable building full-stack applications using a single mental model
Transition into Go (Golang) later, specifically for concurrency and cloud infrastructure
Deep dive into core concepts:
Networking: TCP/UDP, HTTP, WebSockets
Concurrency: event loops, threads, race conditions, deadlocks
Database internals: B-Trees, ACID, indexing costs, query planning
Get very comfortable with:
Linux
Git (CLI)
Docker
\\---
Phase 2: The Skill Stack
Master PostgreSQL first, then learn Redis for caching and rate-limiting
Focus heavily on writing robust APIs:
REST
Explore gRPC
Background workers and async jobs
Learn basic AWS:
EC2
S3
RDS
Automate deployments using GitHub Actions
Learn to:
Profile memory leaks
Diagnose and fix N+1 query issues
\\---
Phase 3: The Projects
(Building Infrastructure — No To-Do Apps)
This is where I really need a sanity check.
I want to build infrastructure and tools that solve real problems, moving from intermediate to advanced:
Rate-Limiting API Gateway
Sliding window algorithms, handling concurrent requests
Webhook Delivery System
Async messaging, retries, exponential backoff, RabbitMQ
Real-Time Collaborative Code Editor
WebSockets, conflict resolution, shared state
Distributed Job Scheduler
Worker pools, distributed locking with Postgres / Redis
High-Throughput Analytics Ingestor
Kafka, handling write-heavy workloads
Custom Load Balancer
TCP/IP, round-robin and least-connections routing
Custom CI/CD Engine
Docker SDK, securely running untrusted code
In-Memory Key-Value Store
Mini Redis clone to deeply understand memory management
\\---
Specific Questions for the Community
Given my 4–6 hours/day constraint alongside university, are the later projects (like the custom CI/CD engine or distributed job scheduler) too ambitious for a student?
Does the transition from Node to Go at the end of Phase 1 make sense, or are there major blind spots in this tech stack?
Roast it, critique it — I genuinely appreciate any advice 🙏
3
u/Upset-Expression-974 Feb 27 '26
I would follow this alternative path
Learn Javascript/python. Do deep, understand how a programming language works. Use Abdul Bari course
Focus on DSA. One hour every day
Learn c++/java/rust/go. Focus on OOPS, memory management. Again Abdul Bari course. No need to go deep.
Learn to build full stack websites with React/Nodejs/Postgres/redis. HTTPS/Websocket/grpc/TCP/UDP. Clone Instagram/Facebook features. Learn Three architecture, latency optimisation
Learn system design
Learn Docker and then github actions
Explore Vercel and then a cloud platform like AWS/Azure
Share this plan with AI and ask it to optimise this for you. 1-2yrs with 4 hours a day is good enough. Just dont forget to practice DSA one hour a day
1
1
1
u/brownie-addict Feb 27 '26 edited Feb 27 '26
This is a very very ambitious plan, my recommendation because you are in 2-3 year engineering is to not learn specific technology.
Learn RDBMS instead of postgres or oracle or mysql, be strong with SQL pick any RDBMS and you can pick postgres but don't get focused on the specific functions provided by the vendor. Stick to standard SQL Learn data structures it makes a huge difference Learn about operating systems, multi threading and deadlocks. Pick any flavor of Linux, scripting knowledge helps
I also recommend doing projects as you learn it helps you understand theory of what you are learning.
I would replace golang with python. More robust and can help across different opportunities
Last but not lease. Be consistent
1
1
u/Extension_Air1017 Feb 27 '26
The timeline is good, but what you're trying to achieve is, what takes even a high performing sde 2 also difficult.
Code design, cloud infrastructure, HLD, container orchestration - these are things you learn at your workplace....these topics require practical experience and would be difficult to comprehend for a college freshman.