🚀 Day 30 - Restarting My Full-Stack Journey Today was a very practical backend development day. Instead of focusing only on theory, I spent most of my time building APIs with Express.js and understanding how routing and middleware work behind the scenes. This was one of those days where concepts started feeling much more real because I could actually see requests moving through my application. 📚 What I learned today: ✅ Express Fundamentals * Creating Express applications * Understanding request and response objects * Working with JSON data using: app.use(express.json()) * Sending responses using: * `res.send()` * `res.json()` * `res.status()` * `res.redirect()` * `res.sendStatus()` ✅ Route Parameters & Query Parameters Worked with: /menu/:id and /search?q=biryani Understanding the difference between: * `req.params` * `req.query` ✅ HTTP Methods in Express Implemented: * GET * POST * PUT * PATCH * DELETE Built CRUD-style APIs and understood where each method should be used. ✅ Express Routing * Route handlers * Dynamic routes * Wildcard routes * Route chaining using: app.route() ✅ Middleware Deep Dive Learned how middleware works in Express: * Request logging middleware * Timing middleware * Authentication middleware * Authorization middleware Understanding: next() and why forgetting it can cause requests to hang forever. ✅ Authentication & Authorization Built custom middleware for: * Token validation * User identification * Role-based access control Understanding the difference between: * Authentication → Who are you? * Authorization → What are you allowed to do? 🛠️ Practical Work Built multiple Express applications that included: ✅ Basic Express Server ✅ Route Parameters ✅ Query Parameters ✅ CRUD Operations ✅ Request Logging ✅ Authentication Middleware ✅ Role-Based Authorization ✅ Custom Response Handling 💡 Biggest takeaway: Today made me realize that middleware is one of the most powerful concepts in backend development. Instead of writing the same code in every route, middleware allows us to handle logging, authentication, validation, and many other concerns in a clean and reusable way. Backend development is starting to feel much more structured and scalable now 🚀 #100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #ExpressJS #JavaScript #APIs #Middleware #LearningInPublic #ChaiCode #DAY1 #DAY30 #100DaysOfSilence @Hiteshdotcom @piyushgarg_dev @yntpdotme @surajtwt_ @ChaiCodeHQ

🚀 Day 29 — Restarting My Full-Stack Journey Today I went deeper into Node.js and learned what actually happens behind the scenes when JavaScript runs outside the browser. This was one of those topics where understanding the internals made many previously confusing concepts finally click. 📚 What I learned today: ✅ How JavaScript Runs in Browsers vs Node.js * Browsers provide Web APIs * Node.js provides Node APIs * Both use JavaScript but have different runtime environments ✅ Understanding Node.js Architecture * V8 JavaScript Engine * Node.js APIs * C/C Bindings * libuv * Event Loop Understanding how all these components work together to execute JavaScript outside the browser. ✅ Node.js Process Lifecycle Learned what happens when we run: ```bash node index.js ``` * A Node.js process is created * A main thread is allocated * Top-level code starts executing * Modules are loaded * Event callbacks are registered * Event loop starts processing tasks ✅ Event Loop Deep Dive Explored major event loop phases: * Timers * I/O Poll Phase * `setImmediate()` * Close Callbacks And how Node.js decides when to continue or exit the process. ✅ Main Thread vs Thread Pool Learned: * JavaScript runs on the main thread * CPU-blocking code can freeze execution * libuv uses a thread pool for certain expensive operations * Why blocking code like `while(true)` should be avoided ✅ Understanding Asynchronous Execution Practiced examples using: * `console.log()` * `setTimeout()` * Event Loop execution order And understood why asynchronous callbacks execute after synchronous code completes. 🛠️ Practice: * Explored Node.js execution flow * Tested event loop behavior using timers * Experimented with callback execution order * Learned how blocking code impacts application performance 💡 Biggest takeaway: Before today, I knew that Node.js was "single-threaded." Now I understand what that actually means. Learning about the event loop, libuv, the main thread, and asynchronous execution helped me understand how Node.js handles thousands of operations efficiently without blocking the application. The deeper I go into backend development, the more fascinating it becomes 🚀 #100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #JavaScript #EventLoop #WebDevelopment #LearningInPublic #ChaiCode #dayxwebtoon #TrendingforPavel #100DaysOfSilence #DAY29 @Hiteshdotcom @nirudhuuu @yntpdotme @ChaiCodeHQ @surajtwt_ @codedailybot @_100DaysOfCode @100days