Understanding Micro Services

  • Understanding Micro Services – Part 1 – Why Monoliths Fail at Scale

    The Breaking Point — Why Monoliths Fail at Scale 1. Architectural Context A monolith works well in the beginning because everything runs in one place – one application, one database, one transaction boundary. When a request comes in, it is processed completely inside a single JVM. If anything fails, everything rolls back. This gives strong…

  • Understanding Micro Services – Part 2 – What Really Changes When You Move

    The Illusion of Micro Services — What Actually Changes The Expectation: Breaking the System Will Make It Simpler When teams decide to move away from a monolith, the decision rarely comes from curiosity. It usually comes from pressure. The system has already started showing signs of strain. Things are slowing down, deployments feel risky, and…

  • Understanding Micro Services – Part 3 – How Micro Services Systems Actually Fail

    How Systems Actually Fail — The Reality of Distributed Failures 1. When Everything Works… Until It Doesn’t By the time a system reaches microservices, it usually looks clean on diagrams. Services are separated, responsibilities are clear, and deployments are independent. From an architectural standpoint, everything appears structured and scalable. Most of the time, the system…

Java Evolution

  • JDK 26 features – Evolution, Understanding the enhancements not just features

  • Evolution of Java from JDK 8 to JDK 25

  • JDK 25 Features Explained with Real-World Understanding

Concurrency

  • Concurrency in Java – Developer’s Perspective

  • Java Thread Creation: Traditional Threads vs ExecutorService vs Virtual Threads

Scroll to Top