anish
@Anishdotcom
Followers
456
Following
8K
Media
49
Statuses
2K
20 • Builder in Beta mode • Scaling @thesubscription • Documenting 0 to 1 chaos •
Joined January 2025
Kicking off a Backend Development 101 series Week 1: Foundations Day 1: HTTP + Request Lifecycle Day 2: Routing, Controllers & Middlewares Day 3: Databases (SQL vs NoSQL) + Modeling Day 4: Authentication, JWT & Password Security Day 5: Error Handling, Logging & Debugging
31
10
135
Made a little side project of all blogs from creators on X https://t.co/kMwBlS8I27 - Filter by creators and topics - Bookmarks and reading status in your dashboard Fully open source if you guys want to include your own blogs, link is in the replies
18
11
46
Lets learn about the core fundamentals of Backend Engineering About Authentication and Authorizations. Many of you learned about JWT tokens which is used to implement user authentication and authorisation system. Most of you have never heard about JOSE JSON Object Signing and
12
10
35
Day 3/14: Databases, Models & Schema Design Topics covered: > Why databases exist > SQL vs NoSQL > Schema & Models > CRUD operations > Relationships between data > Queries > Validation > Indexes
8
4
34
Tomorrow (Day 4): Authentication & Security Topics: > Password hashing (bcrypt) > JWT tokens > Login/signup flow > Protecting routes > Authorization vs Authentication Making your app secure 🔐 Drop a 💚 if databases make sense now!
1
1
20
9/ Indexes Without an index: Database must scan everything. With an index: Database jumps straight to the result. Common indexes: > email (login) > user_id (fetching posts) > createdAt (sorting newest) Indexes make large apps feel fast and scale gracefully.
1
0
15
8/ Validation Good data in → good features out. Validation ensures: > required fields exist > formats are correct > values stay within rules > uniqueness is enforced You don’t want "age": "banana" entering your system. Validation protects your database from future pain.
1
0
11
7/ Queries Databases don’t just store they retrieve intelligently. Most features you use daily (feeds, search, filters) come from just a few query patterns: Find one - > SQL: SELECT * FROM users WHERE id = 1; > MongoDB: db.users.findOne({ id: 1 }) Filter - > SQL: SELECT
1
0
11
6/ Relationships Real-world data isn’t isolated it’s linked. Examples: 1:1 → User ↔ Profile 1:N → User ↔ Posts N:N → Students ↔ Courses, Users ↔ Liked Posts
1
0
11
5/ CRUD Operations CRUD = Create, Read, Update, Delete Without database: > Array methods (push, filter, map) > Gone on restart With database: INSERT → Create new record SELECT → Read/fetch records UPDATE → Modify existing record DELETE → Remove record
1
0
10
4/ Schema: Your Blueprint A schema defines what a valid record looks like. Example (User schema): name → string, required email → string, unique, required password → string, hashed createdAt → auto timestamp Why schemas matter: > Consistency (every user has same fields)
1
0
10
3/ SQL vs NoSQL There are two major styles of structuring data: SQL (Relational) > Data stored in tables (rows & columns) > Like Excel spreadsheets > Strict rules (schema) > Relationships between tables NoSQL (Document-based) > Data stored as documents (JSON-like) >
1
0
10
2/ Why Databases Exist Right now, if I store users like: let users = [{ id: 1, name: "Anish" }] and my server restarts?Everything disappears. A database solves that. It stores data: > Permanently > Safely > Reliably. Memory forgets. Databases remember. That’s called data
2
0
10
Day 3/14: Databases, Models & Schema Design Topics covered: > Why databases exist > SQL vs NoSQL > Schema & Models > CRUD operations > Relationships between data > Queries > Validation > Indexes
8
4
34
Day 2/14: Routing, Controllers & Middlewares Topics I covered today: > Routing > Controllers > Middlewares > Request/Response objects From chaos to structure.... 1/ What is Routing? The problem: > You have 50 different endpoints > /login, /signup, /users, /posts, etc.
14
3
34
Just recorded a quick walkthrough of my metaverse game ! lemme know your thoughts
19
4
44
Complete flow: Tomorrow (Day 3): Databases Topics: > SQL vs NoSQL > When to use which Database modeling > Connecting to DB CRUD operations > From in-memory data to persistent storage 🚀 Drop a 💚 if routing & middlewares click now!
1
0
10
Day 2/14: Routing, Controllers & Middlewares Topics I covered today: > Routing > Controllers > Middlewares > Request/Response objects From chaos to structure.... 1/ What is Routing? The problem: > You have 50 different endpoints > /login, /signup, /users, /posts, etc.
14
3
34
Day 29 ( was an amazing day ) ( Night ) Went sightseeing today. Here are some pics All goals achieved and more ✅
2
1
10
DAY 1: HTTP + Request Lifecycle What I studied today: > Client-Server architecture > HTTP & why it's stateless > Request structure > HTTP methods > Status codes > Request lifecycle Starting from zero. Let's understand how clients and servers talk to each other. 1/ Why
18
3
77