---
title: "ayushsharmaio0112 (@ayushsharma11) | Hashnode"
description: "Software Engineer, curious about distributed systems and AI. Read the latest articles by ayushsharmaio0112 on Hashnode."
url: "https://hashnode.com/@ayushsharma11"
---

@ayushsharma11

# ayushsharmaio0112

@ayushsharma11 · Bangalore, India · Joined August 2026

Software Engineer, curious about distributed systems and AI

### [The One Blocking Call That Broke Our "Non-Blocking" API](https://systemsatscale.hashnode.dev/the-one-blocking-call-that-broke-our-non-blocking-api?utm_source=hashnode&utm_medium=feed)

(Part 2 of 2 — I/O Architecture Series) Quick recap from Part 1: Tomcat gives every request its own thread and blocks it during I/O — simple, but expensive under high concurrency. Netty multiplexes th

7 min read · [systemsatscale.hashnode.dev](https://systemsatscale.hashnode.dev/the-one-blocking-call-that-broke-our-non-blocking-api?utm_source=hashnode&utm_medium=feed)

[Sep 27](https://hashnode.com/posts/the-one-blocking-call-that-broke-our-non-blocking-api/6ab9551cf2f76acd19961877)

### [Tomcat vs Netty: The Thread Model Decision Most Engineers Get Backwards](https://systemsatscale.hashnode.dev/tomcat-vs-netty-the-thread-model-decision-most-engineers-get-backwards?utm_source=hashnode&utm_medium=feed)

Blocking vs non-blocking I/O, Java NIO, and how Tomcat's thread-per-request model compares to Netty's event loop, fundamentals for backend engineer.

7 min read · [systemsatscale.hashnode.dev](https://systemsatscale.hashnode.dev/tomcat-vs-netty-the-thread-model-decision-most-engineers-get-backwards?utm_source=hashnode&utm_medium=feed)

[Sep 14](https://hashnode.com/posts/tomcat-vs-netty-the-thread-model-decision-most-engineers-get-backwards/6aa856159b22743308a36950)

### [Stop Confusing API Gateway, Load Balancer, and Reverse Proxy](https://systemsatscale.hashnode.dev/stop-confusing-api-gateway-load-balancer-and-reverse-proxy?utm_source=hashnode&utm_medium=feed)

If you've ever been in a system design interview or an architecture review and heard someone say "just put a load balancer in front of it" when they actually meant an API Gateway - you're not alone. T

6 min read · [systemsatscale.hashnode.dev](https://systemsatscale.hashnode.dev/stop-confusing-api-gateway-load-balancer-and-reverse-proxy?utm_source=hashnode&utm_medium=feed)

[Aug 22](https://hashnode.com/posts/stop-confusing-api-gateway-load-balancer-and-reverse-proxy/6a8a1020f7dc0a83bca43a18)