Pattern
BFF — Backend for Frontend
A dedicated BFF layer aggregates data from multiple microservices (stocks, MF, auth) into a single partner-friendly API response. Partners get a stable contract; internal services can evolve independently. Reduces partner integration friction dramatically.
Partner App
│
BFF Layer ← single API surface, versioned
┌───┼───┐
│ │ │
StockSvc MFSvc AuthSvc ← internal µservices
Pattern
Cache-Aside with TTL Tiering
Stock prices (volatile) → 5s TTL. NAVs (daily) → 6h TTL. Portfolio summaries (user-specific) → 2min TTL with tag-based invalidation on trade execution. Achieved 40% DB load reduction without stale data issues.
Redis Cache-Aside
TTL tiering
tag invalidation
40% DB load ↓
Pattern
Strangler Fig — Monolith Migration
At Legistify, migrated a Django monolith to microservices using Strangler Fig — incrementally extracting bounded contexts (search, permissions, notifications) behind a facade router, with zero downtime and a 50% performance boost.
Monolith → Facade Router
├── /search → SearchSvc
├── /perms → PermSvc
├── /notify → NotifySvc
└── /legacy → Monolith (shrinking)
Pattern
Outbox + Idempotency for Reliability
Critical financial writes (order creation, SIP execution) use a transactional outbox pattern — the event is written to an outbox table in the same DB transaction as the business record. A poller publishes to SQS; idempotency keys prevent duplicate processing.
DB txn
→
orders + outbox
→
Poller
→
SQS
→
Lambda (dedup)
Certifications & Study
Scaler Academy — DSA · SQL · LLD · HLD
Completed structured curriculum covering Data Structures & Algorithms, advanced SQL and database internals, Low-Level Design (SOLID, design patterns, class modelling), and High-Level Design (distributed systems, CAP theorem, consistent hashing, system design interviews).
Data Structures & Algorithms
Low-Level Design
High-Level Design
Databases & SQL
SOLID principles
Design Patterns
CAP theorem
Consistent hashing
Distributed systems
Certified Credentials
Industry Certifications