---
title: "#concurrent articles | Hashnode"
description: "Explore 43 articles tagged #concurrent on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/concurrent"
---

Tag

# #concurrent

43 posts · 0 followers

[Ahmed Refaat](https://hashnode.com/@refaat1297) · [Nov 9](https://hashnode.com/posts/concurrent-rendering-in-react-19-part-2/6af22d7151cef92a4e25f3ec)

### [Concurrent Rendering in React 19, Part 2: startTransition, useTransition and useDeferredValue](https://refaat1297.hashnode.dev/concurrent-rendering-in-react-19-part-2?utm_source=hashnode&utm_medium=feed)

Typing lags while a big list renders? Learn how startTransition, useTransition, and useDeferredValue keep React 19 UI responsive, with real examples.

16 min read · [refaat1297.hashnode.dev](https://refaat1297.hashnode.dev/concurrent-rendering-in-react-19-part-2?utm_source=hashnode&utm_medium=feed)

[Ahmed Refaat](https://hashnode.com/@refaat1297) · [Oct 7](https://hashnode.com/posts/concurrent-rendering-in-react-19-part-1/6ac657a2dc99c1b9f3a56976)

### [Concurrent Rendering in React 19, Part 1: How React Learned to Pause](https://refaat1297.hashnode.dev/concurrent-rendering-in-react-19-part-1?utm_source=hashnode&utm_medium=feed)

Why does typing lag when React re-renders a big list? Learn how concurrent rendering, Fiber, time slicing, and lanes let React pause for your users.

14 min read · [refaat1297.hashnode.dev](https://refaat1297.hashnode.dev/concurrent-rendering-in-react-19-part-1?utm_source=hashnode&utm_medium=feed)

[Yashika Vijayvargiya](https://hashnode.com/@railswithyashika) · [Jun 15](https://hashnode.com/posts/postgresql-concurrent-indexes-in-rails-avoiding-downtime-in-production/6a2fd3d893fd5e9c7afbdf9c)

### [PostgreSQL Concurrent Indexes in Rails: Avoiding Downtime in Production](https://railswithyashika.hashnode.dev/postgresql-concurrent-indexes-in-rails-avoiding-downtime-in-production?utm_source=hashnode&utm_medium=feed)

When working with large production databases, adding an index may seem like a simple migration. However, on tables with millions of records, a regular index creation can lock writes and impact your application's availability.

4 min read · [railswithyashika.hashnode.dev](https://railswithyashika.hashnode.dev/postgresql-concurrent-indexes-in-rails-avoiding-downtime-in-production?utm_source=hashnode&utm_medium=feed)

[Tuanhdotnet](https://hashnode.com/@tuananh8) · [May 8](https://hashnode.com/posts/techniques-how-to-design-versioned-commands-so-retries-stay-safe-under-concurrent-modification/69fda622a6365f430bd2472c)

### [Techniques: How to design versioned commands so retries stay safe under concurrent modification?](https://tuanhnet.hashnode.dev/techniques-how-to-design-versioned-commands-so-retries-stay-safe-under-concurrent-modification?utm_source=hashnode&utm_medium=feed)

A deep, practical guide on designing versioned command patterns that let automated retries remain safe in the face of concurrent updates. Covers optimistic compare-and-swap, idempotency envelopes, retry policies, distributed versioning, performan...

12 min read · [tuanhnet.hashnode.dev](https://tuanhnet.hashnode.dev/techniques-how-to-design-versioned-commands-so-retries-stay-safe-under-concurrent-modification?utm_source=hashnode&utm_medium=feed)

[Tuanhdotnet](https://hashnode.com/@tuananh8) · [May 4](https://hashnode.com/posts/reasons-java-services-get-slower-after-a-few-hours-how-to-find-thread-pool-saturation/69f8604287b1809c5b024bef)

### [Reasons Java services get slower after a few hours: How to find thread pool saturation?](https://tuanhnet.hashnode.dev/reasons-java-services-get-slower-after-a-few-hours-how-to-find-thread-pool-saturation?utm_source=hashnode&utm_medium=feed)

A practical, deep-dive guide explaining why Java services often slow down after running for hours, how thread-pool saturation produces this pattern, how to detect it with metrics and code, and the concrete fixes and trade-offs engineers should ap...

10 min read · [tuanhnet.hashnode.dev](https://tuanhnet.hashnode.dev/reasons-java-services-get-slower-after-a-few-hours-how-to-find-thread-pool-saturation?utm_source=hashnode&utm_medium=feed)

[Ashish Kumar](https://hashnode.com/@helloashish) · [May 4](https://hashnode.com/posts/react-concurrent-features-urgent-vs-deferred-ui-updates/69f7e898d5d0436ffdaf8372)

### [React Concurrent Features: Urgent vs Deferred UI Updates](https://helloashish.hashnode.dev/react-concurrent-features-urgent-vs-deferred-ui-updates?utm_source=hashnode&utm_medium=feed)

Before React 18, the render cycle was synchronous and uninterruptible. Once React started reconciling a tree, it ran to completion: even if that took 400ms and the user was typing. Every keystroke tha

9 min read · [helloashish.hashnode.dev](https://helloashish.hashnode.dev/react-concurrent-features-urgent-vs-deferred-ui-updates?utm_source=hashnode&utm_medium=feed)

[Tuanhdotnet](https://hashnode.com/@tuananh8) · [May 2](https://hashnode.com/posts/ways-to-invalidate-derived-caches-without-creating-a-distributed-guessing-game/69f5bd3273ab51cfc77bc6c2)

### [Ways to Invalidate Derived Caches Without Creating a Distributed Guessing Game](https://tuanhnet.hashnode.dev/ways-to-invalidate-derived-caches-without-creating-a-distributed-guessing-game?utm_source=hashnode&utm_medium=feed)

Practical, production-ready strategies for invalidating derived caches in distributed systems. Focuses on patterns that avoid brittle TTL-only approaches and race-prone heuristics, with Java examples, performance trade-offs, and operational guida...

11 min read · [tuanhnet.hashnode.dev](https://tuanhnet.hashnode.dev/ways-to-invalidate-derived-caches-without-creating-a-distributed-guessing-game?utm_source=hashnode&utm_medium=feed)

[Tuanhdotnet](https://hashnode.com/@tuananh8) · [Apr 24](https://hashnode.com/posts/methods-to-handle-time-drift-issues-in-distributed-systems/69eb3124b503a1f2acdeb475)

### [Methods to Handle Time Drift Issues in Distributed Systems](https://tuanhnet.hashnode.dev/methods-to-handle-time-drift-issues-in-distributed-systems?utm_source=hashnode&utm_medium=feed)

Practical, in-depth methods for detecting, compensating, and architecting around clock drift in distributed systems. Covers NTP/PTP trade-offs, logical clocks (Lamport, vector, HLC), monotonic timestamp generators, leader-based allocation, failur...

13 min read · [tuanhnet.hashnode.dev](https://tuanhnet.hashnode.dev/methods-to-handle-time-drift-issues-in-distributed-systems?utm_source=hashnode&utm_medium=feed)

[Tuanhdotnet](https://hashnode.com/@tuananh8) · [Apr 21](https://hashnode.com/posts/methods-to-prevent-duplicate-cron-execution-across-multiple-spring-boot-instances/69e73c9d8c53a94725cd2c9a)

### [Methods to Prevent Duplicate Cron Execution Across Multiple Spring Boot Instances](https://tuanhnet.hashnode.dev/methods-to-prevent-duplicate-cron-execution-across-multiple-spring-boot-instances?utm_source=hashnode&utm_medium=feed)

Practical strategies, code patterns, and operational trade-offs to ensure scheduled jobs run exactly once in clustered Spring Boot deployments — with Redis, database locks, ShedLock, Quartz clustering, and Kubernetes leader patterns explained in ...

10 min read · [tuanhnet.hashnode.dev](https://tuanhnet.hashnode.dev/methods-to-prevent-duplicate-cron-execution-across-multiple-spring-boot-instances?utm_source=hashnode&utm_medium=feed)

[Tuanhdotnet](https://hashnode.com/@tuananh8) · [Apr 18](https://hashnode.com/posts/methods-to-handle-zombie-requests-after-the-user-already-closed-the-browser/69e348376091a94a973305aa)

### [Methods to Handle Zombie Requests After the User Already Closed the Browser](https://tuanhnet.hashnode.dev/methods-to-handle-zombie-requests-after-the-user-already-closed-the-browser?utm_source=hashnode&utm_medium=feed)

Practical, in-depth methods to detect and mitigate zombie requests after users close the browser. Covers server-side detection, cancellation strategies in Java (servlets, CompletableFuture, WebSocket), infrastructure controls, performance trade-o...

12 min read · [tuanhnet.hashnode.dev](https://tuanhnet.hashnode.dev/methods-to-handle-zombie-requests-after-the-user-already-closed-the-browser?utm_source=hashnode&utm_medium=feed)
