---
title: "Discussion on \"The One Blocking Call That Broke Our \"Non-Blocking\" API\" | Hashnode"
description: "Discussion on \"The One Blocking Call That Broke Our \"Non-Blocking\" API\". (Part 2 of 2 — I/O Architecture Series)\nQuick 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"
url: "https://hashnode.com/posts/the-one-blocking-call-that-broke-our-non-blocking-api/6ab9551cf2f76acd19961877"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [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

Sep 27 · 7 min read · systemsatscale.hashnode.dev  
Read the article

## Written by

[ayushsharmaio0112](https://hashnode.com/@ayushsharma11)

@ayushsharma11 · Bangalore, India

  
[View profile](https://hashnode.com/@ayushsharma11)

Software Engineer, curious about distributed systems and AI

Software Engineer @ Target | Building reliable, high-scale systems with Kotlin, Java, Spring Boot & Kafka

## Responses

Markdown supported · ⌘↵ to post

No responses yet.