Hello, I'm

Manoj KrushnaMohanta

I build and rescue Java backend systems.

For five years I've built and run Spring Boot services in production across insurance finance, claims and payments. This site runs on my own API, and the live map shows it working.

Live system
YOUbrowserEDGEcloudflareAPIVT 0spring boot 4java 25virtual threadsCACHEcaffeineDBpostgres 18OUTBOXsmtp mail
SteadyHot reads come from the in-process cache in a few ms; misses fall through to PostgreSQL.
12
requests / s
18 ms
p95 latency
74%
cache hits
0
shed (429)
Sample trafficReal architecture of this site
5+
Years of Java in production
120+
Production bugs resolved
60+
Features shipped live
Lead
Graduate trainee to lead in five years
  • Java
  • SQL
  • Spring Boot
  • Spring Security
  • OAuth2.0
  • JWT
  • JAX-RS
  • Hibernate
  • ABS (Allianz Business System)
  • PostgreSQL
  • IBM DB2
  • Apache Kafka
  • Git
  • Jenkins
  • Dynatrace
  • C
  • C++
  • Python
  • JavaScript
  • Dart
  • Flutter
  • MySQL
  • Amazon SQS
  • Grafana
  • Prometheus
  • AWS EC2
  • AWS S3
  • AWS IAM
  • AWS RDS
  • Cloudinary
  • Cloudflare
  • IntelliJ IDEA
  • VS Code
  • Postman
  • Eclipse
  • DBeaver
Tech stack
Daily in productionUsed in projectsFamiliar
Languages
  • Java
  • SQL
  • C
  • C++
  • Python
  • JavaScript
  • Dart
Frameworks & security
  • Spring Boot
  • Spring Security
  • OAuth2.0
  • JWT
  • JAX-RS
  • Hibernate
  • ABS (Allianz Business System)
  • Flutter
Data & messaging
  • PostgreSQL
  • IBM DB2
  • Apache Kafka
  • MySQL
  • Amazon SQS
Observability & delivery
  • Git
  • Jenkins
  • Dynatrace
  • Grafana
  • Prometheus
Cloud & hosting
  • AWS EC2
  • AWS S3
  • AWS IAM
  • AWS RDS
  • Cloudinary
  • Cloudflare
Workbench
  • IntelliJ IDEA
  • VS Code
  • Postman
  • Eclipse
  • DBeaver
Experience
Go Digit General Insurance Co.Team · ABS Core Finance & Institutional
Jul 2021 – now
  1. Lead EngineerApr 2026 – now
    7 mo
  2. Senior Software EngineerApr 2024 – Mar 2026
    2 yrs
  3. Software EngineerJul 2022 – Mar 2024
    1 yr 9 mo
  4. Graduate Trainee EngineerJul 2021 – Jun 2022
    1 yr
Recognition
  • Digit MastermindQ1 2026
  • Wall of Awesome-nessTechnology · Q4 2024-25
Education

B.Tech, Silicon Institute of Technology (BPUT)

2017 – 2021 · CGPA 9.1

Languages

English · हिन्दी · ଓଡ଼ିଆ

Impact

Evidence, not adjectives

Measured results from production systems I built or rescued.

CASE 01 / PerformanceClaim intimation · 32 s → 6 sResolved

Claim intimation: from 32 seconds to 6

A claim-intimation service in a life-insurance platform took about 32 seconds to respond. I traced where the time went and took the slow work off the request path.

−80%response time
  • Spring Boot
  • JAX-RS
  • Async calls
  • Caching
  • Apache Kafka
  1. 01 · Symptom

    Every claim intimation took about 32 seconds to respond.

  2. 02 · Diagnosis

    Dynatrace traces showed far too many service calls behind each request. Logs and the code path confirmed redundant internal and external JAX-RS calls, plus slow database queries.

  3. 03 · Fix

    Async service calls where needed, caching for repeated lookups, and Kafka for the external calls that sync data.

  4. 04 · Result

    Response time down to about 6 seconds, roughly 80% faster.

SystemsDesigned and builtServices and major features I own end to end
SYS 01

Premium receipting service

Called by the payment gateway to validate the premium paid against the amount due, then create the booking and receipting entries in ABS and trigger the policy or process transition. Payment events go to Amazon SQS over OAuth2.0.

  • Gateway callback
  • ABS
  • Amazon SQS
  • OAuth2.0
SYS 02

Kafka notification pipeline

Migrated the SMS, email and WhatsApp notification services previously run by the finance team onto Kafka: event-driven, asynchronous and decoupled from the request path.

  • Apache Kafka
  • Event-driven
  • SMS · Email · WhatsApp
SYS 03

Life-insurance claims and policy platform

Greenfield backend for a new life-insurance business: the full claim lifecycle (intimation, settlement, payout, cancellation), premium receipting and policy issuance, developed from scratch.

  • REST APIs
  • Greenfield
  • Claims · Policy issuance
SYS 04

General-insurance claim payouts

Integrated the settlement, costing and payout services into the general-insurance claims flow, then merged and optimised that flow to cut its response time.

  • Service integration
  • Settlement
  • Costing
SYS 05

Payout and rebooking ledger

Creates bookings and keeps balances consistent across agent, customer, contract and internal accounts.

  • Bookings
  • Account balances
SYS 06

Premium, tax and refund engine

Product-specific calculation logic for premium, tax and refunds across multiple insurance products.

  • Calculation logic
  • Multi-product
3D Lab / Chapter modeIncident replays · 01 / 05Preview

Walk the server hall. Find the culprit.

Each chapter replays a production incident. The loudest alarm is rarely the cause. Try the first one: pick the component you would investigate.

Open the case file in 3D Eight rooms, one verdict · about 3 minutes
Chapter 01 · Checkout freezes at peak0 guesses

$Checkout is freezing at peak. Six components, one root cause. Click the one you would investigate first.

×Traffic is up 40%, but the edge is passing it through without trouble.

×This is where users feel it, not where it starts. Its threads are blocked, waiting for something.

×The loudest alarm, but a symptom: its CPU is high because waiting API threads keep retrying it.

✓Found it. All 50 connections are taken, so every request queues for one. A slow report query was holding them open; the fix is a pool timeout, a separate pool for reports and a faster query.

×Calm at 21% CPU. Requests are not even reaching it fast enough to strain it.

×No lag. The orders that get through are processed straight away.

Research

Systems I study and build

System designs, incident breakdowns and builds. Made on my own time.

04
Tracks
18
Chapters
10
Published
PublishedPlayablePlannedDrafting
Track 01 · SD

System design

05chapters

Five systems taken end to end: requirements, capacity, diagrams, failure modes and how each one scales.

5 of 5 published
  1. SD-01Parking Lot ManagementOOP · State machines · ConcurrencyPublished
  2. SD-02URL ShortenerCaching · Key generation · Read scalingPublished
  3. SD-03Distributed Rate LimiterRedis · Algorithms · AtomicityPublished
  4. SD-04Notification PlatformKafka · Retries · Delivery guaranteesPublished
  5. SD-05Order Management SystemTransactions · Sagas · OutboxPublished
Start with chapter 01
Track 02 · PI

Prod issues

06chapters

Production incidents replayed as case files. The loudest alarm is rarely the cause.

2 of 6 published
  1. PI-01Claim intimation: 32 s to 6 sTraces · async calls · KafkaPlayable
  2. PI-02Checkout freezes at peakFind the culprit in the 3D LabPlayable
  3. PI-03Kafka consumer falls behindNotificationsPlanned
  4. PI-04Cache entries expire togetherLogin and sessionsPlanned
  5. PI-05Memory fills until it crashesNightly batch jobPlanned
  6. PI-06Retries overload the systemPayment integrationPlanned
Open the 3D case file
Track 03 · ST

Stories

04chapters

Notes from the field: the decisions behind the work, told plainly, with what I would do differently.

0 of 4 published
  1. ST-01Moving SMS, email and WhatsApp onto KafkaMigration · async messagingDrafting
  2. ST-02Reading a slow request in DynatraceObservability · debuggingDrafting
  3. ST-03A portfolio that runs on its own APISpring Boot · AstroDrafting
  4. ST-04Making 3D people look real in a browserThree.js · performanceDrafting
First chapters in draft
Résumé

The one-page version

My experience, skills and results on one page, in a plain format that recruiters and applicant tracking systems read cleanly.

  1. 01Summary
  2. 02Skills
  3. 03Experience
  4. 04Awards
  5. 05Education
Contact

Let's build something that stays up.

Hiring for a backend or lead role, planning a project, or just curious? Send a message and it lands straight in my inbox.

Or email me directly
What is this about?