<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sreya Satheesh</title>
    <description>The latest articles on DEV Community by Sreya Satheesh (@sreya-satheesh).</description>
    <link>https://dev.to/sreya-satheesh</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3754294%2F127d6f75-c38d-4d4f-a215-585e5ffb0832.png</url>
      <title>DEV Community: Sreya Satheesh</title>
      <link>https://dev.to/sreya-satheesh</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sreya-satheesh"/>
    <language>en</language>
    <item>
      <title>The Bits Behind the Magic</title>
      <dc:creator>Sreya Satheesh</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:38:28 +0000</pubDate>
      <link>https://dev.to/sreya-satheesh/the-bits-behind-the-magic-1i76</link>
      <guid>https://dev.to/sreya-satheesh/the-bits-behind-the-magic-1i76</guid>
      <description>&lt;p&gt;We use apps and websites every day. We send messages, search for things, watch videos, and share files. But have you ever wondered about all the little things that make these experiences work?&lt;/p&gt;

&lt;p&gt;How does a browser find a website? How does data travel across the internet? How do applications talk to each other? What happens when a server goes down?&lt;/p&gt;

&lt;p&gt;I've always enjoyed exploring how these things work. I wanted to create something that would let people see these concepts in action, interact with them, and experiment with how they work.&lt;/p&gt;

&lt;p&gt;That's how &lt;a href="https://bits-and-pieces-sigma.vercel.app/" rel="noopener noreferrer"&gt;&lt;strong&gt;Bits &amp;amp; Pieces&lt;/strong&gt;&lt;/a&gt; came about.&lt;/p&gt;

&lt;p&gt;It's a collection of 33 interactive exhibits covering the building blocks of system design. Each concept has its own visual playground where you can see what's happening and try things out for yourself.&lt;/p&gt;

&lt;p&gt;You can explore how DNS finds a website, how TCP keeps packets in order, how APIs and message queues work, and how caching helps applications respond faster.&lt;/p&gt;

&lt;p&gt;There's plenty more to explore, including cloud computing, proxies, databases, scalability, availability, fault tolerance, logging, and monitoring.&lt;/p&gt;

&lt;p&gt;The exhibits are grouped into seven areas, from networking and infrastructure to databases and observability.&lt;/p&gt;

&lt;p&gt;I really enjoyed working on Bits &amp;amp; Pieces, especially finding ways to make each concept visual and interactive. I hope you have fun exploring it!&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://bits-and-pieces-sigma.vercel.app/" rel="noopener noreferrer"&gt;Explore Bits &amp;amp; Pieces&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>networking</category>
      <category>systemdesign</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What Happens After You Press Send?</title>
      <dc:creator>Sreya Satheesh</dc:creator>
      <pubDate>Sat, 03 Oct 2026 11:18:17 +0000</pubDate>
      <link>https://dev.to/sreya-satheesh/what-happens-when-you-send-a-whatsapp-message-3ldg</link>
      <guid>https://dev.to/sreya-satheesh/what-happens-when-you-send-a-whatsapp-message-3ldg</guid>
      <description>&lt;p&gt;Think about the last time you sent someone a WhatsApp message.&lt;/p&gt;

&lt;p&gt;You typed a few words, hit Send, saw a tick, and carried on with your day. Maybe the other person replied a few seconds later. Maybe they were offline and replied much later.&lt;/p&gt;

&lt;p&gt;Have you ever stopped to think about everything that happens between those two phones?&lt;/p&gt;

&lt;p&gt;A message has to travel somewhere. The system has to figure out where to send it, make sure it reaches the right person, keep it safe if they're offline, and let you know when it's delivered or read.&lt;/p&gt;

&lt;p&gt;And that's just one message between two people.&lt;/p&gt;

&lt;p&gt;I wanted to explore how all of this works, and that became &lt;a href="https://whats-up-ivory.vercel.app/" rel="noopener noreferrer"&gt;&lt;strong&gt;What's Up?&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The idea was to take a familiar WhatsApp conversation and use it to explore the system behind it.&lt;/p&gt;

&lt;p&gt;You start with Eva sending Sam a simple message:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Hey 👋&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;From there, you can follow the message as it travels through the system. See how it reaches a server, how the system finds Sam's connection, and what happens when Sam isn't online.&lt;/p&gt;

&lt;p&gt;You can also experiment with the system. Break things, remove components, and see what happens to the message. What if an acknowledgement gets lost? What if the same message arrives twice? What if a server goes down?&lt;/p&gt;

&lt;p&gt;As you explore, more pieces of the system come into the picture.&lt;/p&gt;

&lt;p&gt;You'll get to see how WebSockets keep connections open, how messages are routed, how offline messages are stored, and how acknowledgements, retries, and deduplication work.&lt;/p&gt;

&lt;p&gt;Then there are photos and videos, group chats, online status, databases, queues, partitioning, replication, scaling, and encryption.&lt;/p&gt;

&lt;p&gt;Each of these brings its own set of problems and decisions. You can explore them as part of the same messaging system and see how they fit together.&lt;/p&gt;

&lt;p&gt;I had a lot of fun building this one.&lt;/p&gt;

&lt;p&gt;If you've ever wanted to know what happens after you press Send, I'd love for you to give it a try.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://whats-up-ivory.vercel.app/" rel="noopener noreferrer"&gt;Explore What's Up?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>backend</category>
      <category>systemdesign</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What Happens in Those Few Seconds After You Request an OTP?</title>
      <dc:creator>Sreya Satheesh</dc:creator>
      <pubDate>Thu, 01 Oct 2026 07:34:25 +0000</pubDate>
      <link>https://dev.to/sreya-satheesh/the-one-time-password-48j4</link>
      <guid>https://dev.to/sreya-satheesh/the-one-time-password-48j4</guid>
      <description>&lt;p&gt;You enter your phone number or email address, tap &lt;strong&gt;Send OTP&lt;/strong&gt;, and wait.&lt;/p&gt;

&lt;p&gt;A six-digit code arrives. You enter it, tap Verify, and you're done.&lt;/p&gt;

&lt;p&gt;We do this when logging in, making payments, resetting passwords, and verifying accounts. It has become such a familiar part of using apps that we rarely think about what happens between tapping that button and getting access.&lt;/p&gt;

&lt;p&gt;But there's a whole process running in those few seconds.&lt;/p&gt;

&lt;p&gt;The system needs to generate a code, store it, send it to you, start a timer, and wait for you to enter it. When you do, it needs to check whether the code is correct, whether it's still valid, and whether it has already been used.&lt;/p&gt;

&lt;p&gt;I wanted to explore what happens behind this familiar little interaction. That led me to build &lt;a href="https://the-one-time-password.vercel.app/" rel="noopener noreferrer"&gt;&lt;strong&gt;The One Time Password&lt;/strong&gt;&lt;/a&gt;, an interactive walkthrough where you can follow an OTP through its journey and experiment with how the service works.&lt;/p&gt;

&lt;h2&gt;
  
  
  Let's generate an OTP
&lt;/h2&gt;

&lt;p&gt;The walkthrough starts with an OTP request.&lt;/p&gt;

&lt;p&gt;Follow the request as it reaches the API. See how the OTP service generates a code, stores it in Redis with an expiry time, and sends it through an SMS or email provider.&lt;/p&gt;

&lt;p&gt;Once the code is generated, the timer starts ticking.&lt;/p&gt;

&lt;p&gt;What is the service keeping track of while you're looking at that countdown? Where is the OTP stored? How does the system know which user it belongs to? What happens when you enter the code?&lt;/p&gt;

&lt;p&gt;You can follow these steps and see how the different parts of the service work together.&lt;/p&gt;

&lt;h2&gt;
  
  
  What if you try something different?
&lt;/h2&gt;

&lt;p&gt;The interesting part is being able to experiment with the flow.&lt;/p&gt;

&lt;p&gt;What happens if you enter the wrong code? What if you wait until the timer runs out? Can you use the same code again after verification? What if you keep requesting new OTPs?&lt;/p&gt;

&lt;p&gt;These are not just edge cases. They're important decisions in designing an OTP service.&lt;/p&gt;

&lt;p&gt;You can explore how verification attempts are tracked, how rate limiting works, how expired codes are handled, and how the service prevents an OTP from being reused.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens when more people start using it?
&lt;/h2&gt;

&lt;p&gt;The same flow that works for one person needs to work for thousands or millions of people too.&lt;/p&gt;

&lt;p&gt;Now there are multiple application servers handling requests, shared OTP data in Redis, and SMS or email providers delivering codes to users. The system also needs to deal with things like a Redis failure or a slow delivery provider.&lt;/p&gt;

&lt;p&gt;The walkthrough takes you further into the requirements, capacity estimation, and high-level design behind the service.&lt;/p&gt;

&lt;p&gt;An OTP might only be six digits, and the whole interaction might take a few seconds. But there's a lot of engineering behind making those few seconds work reliably.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://the-one-time-password.vercel.app/" rel="noopener noreferrer"&gt;Try The One Time Password&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>systemdesign</category>
      <category>backend</category>
      <category>webdev</category>
      <category>security</category>
    </item>
    <item>
      <title>Inside a Rate Limiter</title>
      <dc:creator>Sreya Satheesh</dc:creator>
      <pubDate>Thu, 18 Jun 2026 08:05:53 +0000</pubDate>
      <link>https://dev.to/sreya-satheesh/behind-every-429-too-many-requests-pfn</link>
      <guid>https://dev.to/sreya-satheesh/behind-every-429-too-many-requests-pfn</guid>
      <description>&lt;p&gt;Imagine an elevator in a busy building. It can carry only a few people at a time. When more people arrive, some have to wait for the next trip. That's how the elevator keeps things moving without getting overloaded.&lt;/p&gt;

&lt;p&gt;Applications face a similar problem.&lt;/p&gt;

&lt;p&gt;Every time someone logs in, searches, refreshes a page, or uses an API, a request reaches the server. When too many requests arrive at once, the application can slow down, become overloaded, or spend resources unnecessarily.&lt;/p&gt;

&lt;p&gt;This is where a &lt;strong&gt;rate limiter&lt;/strong&gt; comes in. It controls how many requests are allowed through and helps keep the application stable.&lt;/p&gt;

&lt;p&gt;I wanted to explore rate limiters from the ground up: understand what they do, see why applications need them, and follow the process of designing one, from the requirements to the final architecture.&lt;/p&gt;

&lt;p&gt;That became &lt;a href="https://rate-limiter-two.vercel.app/" rel="noopener noreferrer"&gt;&lt;strong&gt;Rate Limiter&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The walkthrough starts with a simple visual example. You can see requests arriving, understand how the rate limiter handles them, and see the difference it makes when there's a sudden burst of traffic.&lt;/p&gt;

&lt;p&gt;From there, the focus shifts to the things we need to think about when building one.&lt;/p&gt;

&lt;p&gt;What should the rate limiter keep track of? How does it identify who's sending requests? What should happen when someone reaches their limit? And how do we make sure the rate limiter is available, fast, and efficient?&lt;/p&gt;

&lt;p&gt;You'll explore the functional and non-functional requirements and see how they shape the system we're designing.&lt;/p&gt;

&lt;p&gt;Then comes capacity estimation. We start thinking about the number of users, the requests they generate, the storage needed for counters, and the network bandwidth. The numbers give us a sense of the scale we're designing for.&lt;/p&gt;

&lt;p&gt;Finally, all these pieces come together in the high-level design.&lt;/p&gt;

&lt;p&gt;You can follow the architecture step by step, starting with where the rate limiter should sit, then tracing the request flow, looking at request counters and rate-limiting rules, and bringing everything together in the complete architecture.&lt;/p&gt;

&lt;p&gt;I wanted this to be a visual way to explore rate limiter design, from understanding the basic idea to seeing how the whole system fits together.&lt;/p&gt;

&lt;p&gt;If you've been curious about rate limiters or want to understand how one is designed, come take a look.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://rate-limiter-two.vercel.app/" rel="noopener noreferrer"&gt;Explore Rate Limiter&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>systemdesign</category>
      <category>backend</category>
      <category>ratelimiter</category>
    </item>
    <item>
      <title>Can You Watch an Algorithm Find Its Answer?</title>
      <dc:creator>Sreya Satheesh</dc:creator>
      <pubDate>Thu, 11 Jun 2026 05:45:07 +0000</pubDate>
      <link>https://dev.to/sreya-satheesh/what-if-dsa-was-taught-visually-instead-of-just-theory-4fgf</link>
      <guid>https://dev.to/sreya-satheesh/what-if-dsa-was-taught-visually-instead-of-just-theory-4fgf</guid>
      <description>&lt;p&gt;Take the Two Sum problem.&lt;/p&gt;

&lt;p&gt;You have an array of numbers and a target. You need to find two numbers that add up to that target.&lt;/p&gt;

&lt;p&gt;You might know how to solve Two Sum. But what actually happens when the algorithm runs? Which numbers does it check? How does it keep track of the numbers it has already seen? And how does it know when it has found the pair?&lt;/p&gt;

&lt;p&gt;That's the idea behind &lt;strong&gt;&lt;a href="https://www.decoded-app.com/" rel="noopener noreferrer"&gt;Decoded&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;I wanted to build something where you could take a DSA problem, try your own input, and actually watch the algorithm solve it.&lt;/p&gt;

&lt;h2&gt;
  
  
  See how a problem is solved
&lt;/h2&gt;

&lt;p&gt;Let's take Two Sum again.&lt;/p&gt;

&lt;p&gt;You can enter an array and a target, then start the animation. Watch the algorithm go through the numbers, see how the HashMap changes, and follow the checks it makes until it finds the two numbers.&lt;/p&gt;

&lt;p&gt;Try a different input. Use duplicate numbers, negative numbers, or zeros. See how the algorithm handles them.&lt;/p&gt;

&lt;p&gt;Once you've watched the dry run, you can explore the follow-up questions, understand why a HashMap is used, look at the time and space complexity, and read the Java solution with comments explaining each line.&lt;/p&gt;

&lt;p&gt;There are other problems to explore too, including Longest Substring Without Repeating Characters, Capacity To Ship Packages Within D Days, Merge Intervals, Subarray Sum Equals K, and Top K Frequent Elements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Play around with data structures
&lt;/h2&gt;

&lt;p&gt;Decoded also has a section for data structures like Arrays, Linked Lists, Stacks, Queues, Trees, Graphs, Heaps, and Hash Maps.&lt;/p&gt;

&lt;p&gt;You can explore what each one looks like, its different types, and how its operations work through interactive animations.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get familiar with DSA patterns
&lt;/h2&gt;

&lt;p&gt;Sliding Window, Two Pointers, Prefix Sum, DFS, BFS, and many others.&lt;/p&gt;

&lt;p&gt;Decoded has a section dedicated to these patterns, where you can explore the approach, its different types, and the problems where they're commonly used.&lt;/p&gt;

&lt;p&gt;For example, the Sliding Window section covers fixed-size, variable-size, and frequency-based windows. Each has an animation showing how it works, along with common problems that use the pattern.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens as the input grows?
&lt;/h2&gt;

&lt;p&gt;How much more work does an algorithm do when the input gets bigger? And how much extra memory does it need?&lt;/p&gt;

&lt;p&gt;Decoded has a section dedicated to Time and Space Complexity. You can switch between growth rates like O(1), O(log n), O(n), O(n log n), and O(n²), change the input size, and watch how the number of steps grows on the graph.&lt;/p&gt;

&lt;h2&gt;
  
  
  Explore Decoded
&lt;/h2&gt;

&lt;p&gt;There's a lot of DSA to explore, and I wanted to bring these different pieces together in one place.&lt;/p&gt;

&lt;p&gt;You can explore coding problems, play around with data structures, try different DSA patterns, and see how algorithms behave through the visualizations.&lt;/p&gt;

&lt;p&gt;I hope you enjoy exploring it as much as I enjoyed putting it together.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://www.decoded-app.com/" rel="noopener noreferrer"&gt;Explore Decoded&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>dsa</category>
      <category>programming</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I Love Learning Languages. So I Built One for Malayalam.</title>
      <dc:creator>Sreya Satheesh</dc:creator>
      <pubDate>Tue, 12 May 2026 08:35:56 +0000</pubDate>
      <link>https://dev.to/sreya-satheesh/aksharam-a-tribute-to-my-mother-tongue-kh5</link>
      <guid>https://dev.to/sreya-satheesh/aksharam-a-tribute-to-my-mother-tongue-kh5</guid>
      <description>&lt;p&gt;I enjoy learning new languages. Every language has its own words, sounds, and ways of expressing things. I love discovering all of that.&lt;/p&gt;

&lt;p&gt;But there's one language that's especially close to me: Malayalam, my mother tongue.&lt;/p&gt;

&lt;p&gt;Growing up in Kerala, Malayalam was part of everyday life. I've always wanted to create something around the language, and that idea eventually became &lt;strong&gt;&lt;a href="https://aksharam-app.vercel.app/" rel="noopener noreferrer"&gt;Aksharam&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;അക്ഷരം (Aksharam) means letter in Malayalam.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Aksharam is a Malayalam learning app for beginners. It starts with the basics and takes you through letters, words, and sentences.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting started with Malayalam
&lt;/h2&gt;

&lt;p&gt;The app covers vowels, consonants, chillu letters, compound letters, vowel signs, words, and sentences.&lt;/p&gt;

&lt;p&gt;You can explore the letters, listen to their pronunciation, and follow the English transliteration. The word section introduces everyday Malayalam vocabulary too.&lt;/p&gt;

&lt;h2&gt;
  
  
  A little something for Malayalam
&lt;/h2&gt;

&lt;p&gt;Building Aksharam gave me a chance to do something for a language that's been part of my life since childhood.&lt;/p&gt;

&lt;p&gt;It's still a work in progress, and I have more I'd love to add. For now, I'm simply happy to put it out there and share a little piece of my mother tongue.&lt;/p&gt;

&lt;p&gt;If you'd like to learn Malayalam, come take a look!&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://aksharam-app.vercel.app/" rel="noopener noreferrer"&gt;Explore Aksharam&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>learningapp</category>
      <category>webdev</category>
      <category>programming</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
