---
title: "Saurabh Ravte (@saurabhravte) | Hashnode"
description: "developer. Read the latest articles by Saurabh Ravte on Hashnode."
url: "https://hashnode.com/@saurabhravte"
---

@saurabhravte

# Saurabh Ravte

@saurabhravte · https://localhost:india · Joined February 2026

developer

### [Building Scalable Systems: Caching, Rate Limiting and Observability](https://saurabh-ravte.hashnode.dev/building-scalable-systems-caching-rate-limiting-and-observability?utm_source=hashnode&utm_medium=feed)

Why Applications Need to Scale What scalability means Scalability is your system's ability to handle more users, more requests, and more data — without falling over or slowing to a crawl. Vertical vs

13 min read · [saurabh-ravte.hashnode.dev](https://saurabh-ravte.hashnode.dev/building-scalable-systems-caching-rate-limiting-and-observability?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/building-scalable-systems-caching-rate-limiting-and-observability/6a4d04f4a9a1ad5398e29d2c)

### [Kafka Explained Like You're 5: Events, Partitions, and Consumer Groups](https://saurabh-ravte.hashnode.dev/kafka-explained-like-you-re-5-events-partitions-and-consumer-groups?utm_source=hashnode&utm_medium=feed)

Why Systems Need Event Streaming The old way: request-response In the old way of building apps, one service directly asks another service for something and waits for an answer. This is called request-

10 min read · [saurabh-ravte.hashnode.dev](https://saurabh-ravte.hashnode.dev/kafka-explained-like-you-re-5-events-partitions-and-consumer-groups?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/kafka-explained-like-you-re-5-events-partitions-and-consumer-groups/6a4d03660cf87d7cfd1ecba0)

### [Modern Next.js: Routing, Layouts, Server Components, API Routes & Server Actions](https://saurabh-ravte.hashnode.dev/modern-next-js-routing-layouts-server-components-api-routes-server-actions?utm_source=hashnode&utm_medium=feed)

the App Router, layouts, Server and Client Components, API Routes, and Server Actions — how a SaaS dashboard is actually put together.

8 min read · [saurabh-ravte.hashnode.dev](https://saurabh-ravte.hashnode.dev/modern-next-js-routing-layouts-server-components-api-routes-server-actions?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/modern-next-js-routing-layouts-server-components-api-routes-server-actions/6a4cfc76d15565d8ad3f21ba)

### [Next.js Explained: Why It Became the Default React Framework](https://saurabh-ravte.hashnode.dev/next-js-explained-why-it-became-the-default-react-framework?utm_source=hashnode&utm_medium=feed)

Why Next.js Exists A typical "React-only" app is built with a tool like Vite: it ships one nearly-empty HTML page, and a big bundle of JavaScript that builds the entire UI in the browser. That approac

7 min read · [saurabh-ravte.hashnode.dev](https://saurabh-ravte.hashnode.dev/next-js-explained-why-it-became-the-default-react-framework?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a4ca2015bf583a18c79b35d)

### [React Fundamentals: Components, JSX, State, and Re-rendering](https://saurabh-ravte.hashnode.dev/react-fundamentals-components-jsx-state-and-re-rendering?utm_source=hashnode&utm_medium=feed)

Why did developers create React when JavaScript already existed? JavaScript could already change what's on a web page. So why did an entire library get built on top of it? Because as soon as interface

9 min read · [saurabh-ravte.hashnode.dev](https://saurabh-ravte.hashnode.dev/react-fundamentals-components-jsx-state-and-re-rendering?utm_source=hashnode&utm_medium=feed)

[Jul 6](https://hashnode.com/posts/react-fundamentals-components-jsx-state-and-re-rendering/6a4b8b15360fd5a6b0ac0b06)
