---
title: "Nishant Bhandari (@nishant4532) | Hashnode"
description: "👨‍💻 Associate Software Engineer at Motadata ⭐| Network Monitoring & Observability | Java, JavaScript, Golang 🌐"
url: "https://hashnode.com/@nishant4532"
---

@nishant4532

# Nishant Bhandari

@nishant4532 · Joined June 2024

👨‍💻 Associate Software Engineer at Motadata ⭐| Network Monitoring & Observability | Java, JavaScript, Golang 🌐

[Website](https://portfolio2-five-lilac.vercel.app/)

### [Go vs Vert.x vs Node.js vs Spring Boot: Complete Performance & Cost Comparison (2026)](https://java-insights.hashnode.dev/go-vs-vert-x-vs-node-js-vs-spring-boot-complete-performance-cost-comparison-2026?utm_source=hashnode&utm_medium=feed)

Compare Go, Vert.x, Node.js, and Spring Boot across performance, concurrency, memory usage, latency, and cloud cost in 2026.

6 min read · [java-insights.hashnode.dev](https://java-insights.hashnode.dev/go-vs-vert-x-vs-node-js-vs-spring-boot-complete-performance-cost-comparison-2026?utm_source=hashnode&utm_medium=feed)

[Sep 26](https://hashnode.com/posts/go-vs-vert-x-vs-node-js-vs-spring-boot-complete-performance-cost-comparison-2026/6ab7c40c70ccbbb308730c29)

### [ZGC Deep Dive: How the Ultra-Low Latency Collector Conquers the Heap](https://java-insights.hashnode.dev/zgc-deep-dive-how-the-ultra-low-latency-collector-conquers-the-heap?utm_source=hashnode&utm_medium=feed)

In the JVM world, Garbage Collection has historically carried a non-negotiable tax: the Stop-The-World (STW) pause. While regional collectors like G1GC bounded these pauses using dynamic heuristics, t

7 min read · [java-insights.hashnode.dev](https://java-insights.hashnode.dev/zgc-deep-dive-how-the-ultra-low-latency-collector-conquers-the-heap?utm_source=hashnode&utm_medium=feed)

[Sep 5](https://hashnode.com/posts/zgc-deep-dive-how-the-ultra-low-latency-collector-conquers-the-heap/6a9bd37463efbd5bba1a0207)

### [G1GC Deep Dive: How G1 Actually Works Under the Hood](https://java-insights.hashnode.dev/g1gc-deep-dive-how-g1-actually-works-under-the-hood?utm_source=hashnode&utm_medium=feed)

When a Java application runs, objects are allocated continuously: User user = new User(); Order order = new Order(); List<Order> orders = new ArrayList<>(); Most instances die within milliseconds, wh

8 min read · [java-insights.hashnode.dev](https://java-insights.hashnode.dev/g1gc-deep-dive-how-g1-actually-works-under-the-hood?utm_source=hashnode&utm_medium=feed)

[Sep 5](https://hashnode.com/posts/g1gc-deep-dive-how-g1-actually-works-under-the-hood/6a9bb5a23d51aa136d44fa7c)

### [Memory Leak vs High Memory Usage in Java — A Practical Explanation](https://java-insights.hashnode.dev/memory-leak-vs-high-memory-usage-in-java-a-practical-explanation?utm_source=hashnode&utm_medium=feed)

Stop confusing workload spikes with bugs. Learn the key differences between high memory usage and memory leaks in Java, how to read GC patterns, and t

4 min read · [java-insights.hashnode.dev](https://java-insights.hashnode.dev/memory-leak-vs-high-memory-usage-in-java-a-practical-explanation?utm_source=hashnode&utm_medium=feed)

[Mar 14](https://hashnode.com/posts/memory-leak-vs-high-memory-usage-in-java-a-practical-explanation/69b59f0a210c74252f133a88)

### [Why Reactive Java is Needed: Scaling Beyond Traditional Spring Boot](https://java-insights.hashnode.dev/why-reactive-java-is-needed-scaling-beyond-traditional-spring-boot?utm_source=hashnode&utm_medium=feed)

Learn why Reactive Java is essential for building scalable systems. Compare traditional Spring Boot with Spring WebFlux and Vert.x, and understand event loo

3 min read · [java-insights.hashnode.dev](https://java-insights.hashnode.dev/why-reactive-java-is-needed-scaling-beyond-traditional-spring-boot?utm_source=hashnode&utm_medium=feed)

[Jan 17](https://hashnode.com/posts/why-reactive-java-is-needed-scaling-beyond-traditional-spring-boot/696b6453d0be7d24c67bf058)
