[ 03 ] · Projects

PROOF, NOT
PROMISES.

Distributed systems and microservices platforms — architecture, tradeoffs, and code you can inspect.

Count: 02
Domain: Fintech / Backend
License: MIT

Verified_Modules.log

2 / 2 shown

Case_Studies

Problem, approach, and the architecture that came out the other side — for the modules that earned a deeper look.

[ 01 ] · MODULE_ARYA_BANKING

Arya Banking

// Problem
Synchronous service coordination created cascading failures — a downed auth service froze onboarding and admin actions at once. Event publishing was also unreliable: a failed Kafka write after the DB commit meant the state change was lost forever (dual-write problem).
// Approach
Kafka topics per bounded context with no direct HTTP dependencies between core flows. Built a transactional outbox starter library — the business change and outbox record commit in one MongoDB transaction, then a scheduled relay publishes to Kafka through Schema Registry with bounded retries, guaranteeing at-least-once delivery. All artifacts share Avro contracts and are published via GitHub Packages.
// Impact
  • ✓Transactional outbox guarantees at-least-once event delivery — no dual-write loss
  • ✓Avro contracts on Confluent Schema Registry make schema evolution safe
  • ✓10-repo org with shared libraries and a 100+ page docs site
  • ✓New service onboarding reduced to producer/consumer wiring
architecture.txtASCII
  Client → [API Gateway] ⇄ Keycloak
                │
                ▼
         [Eureka Registry]
         ┌───────┼────────┐
         ▼       ▼        ▼
      [User]  [Auth]   [Admin]
         │       │        │
      MongoDB  Keycloak  Vault
         │
         ▼
  [Outbox] → Kafka → [Schema Registry]
[ 02 ] · MODULE_SB_MICROSERVICES

Spring Boot Microservices Banking

// Problem
Shared-database monoliths meant one schema migration blocked every team and every deploy. Ownership of banking domains was blurred across services.
// Approach
Database-per-service with Eureka discovery, Spring Cloud Gateway routing, and Feign for typed inter-service calls. Keycloak centralizes identity without leaking auth into every service.
// Impact
  • ✓5 independently deployable services, 5 dedicated MySQL schemas
  • ✓Typed Feign clients eliminated hand-rolled REST plumbing
  • ✓Gateway-level auth removed 100% of duplicated security code
architecture.txtASCII
  Client → [Cloud Gateway] ⇄ Keycloak
                │
                ▼
         [Eureka Registry]
         ┌──────┼──────┐
         ▼      ▼      ▼
      [Users][Accts][Txn]  ← Feign clients
         │      │      │
       MySQL  MySQL  MySQL

Coding_Activity

via WakaTime · last 7 days

© 2026 Karthik KulkarniUTF-8 // Blueprint_1.0