Santosh Kumar Tripathi
Software Architect
I design resilient enterprise systems and connect modern cloud platforms with practical AI-enabled capabilities that strengthen business outcomes.
My Engineering Philosophy
I enjoy designing backend systems where reliability, maintainability, and simplicity matter more than architectural trends. Over the years I've worked across healthcare, financial services, and product lifecycle management (PLM), and one lesson keeps repeating itself: the best architecture is rarely the most complex one. Most production problems come from unnecessary complexity rather than a lack of patterns. That perspective shapes how I approach architecture reviews, modernization initiatives, and distributed systems.
Architecture Case Studies
A selection of practical architecture work focused on system boundaries, integration patterns, and business-aligned delivery.
Enterprise Application Observability: A Pragmatic Approach with OpenTelemetry
A practical observability architecture using logs, metrics, traces, and correlation IDs to improve diagnostics, operational visibility, and production support for enterprise applications.
Coming SoonModernizing Legacy Enterprise Systems with the Strangler Fig Pattern
A phased modernization strategy that replaces legacy systems incrementally, reducing migration risk while allowing new capabilities to be delivered without disrupting existing operations.
Coming SoonEnterprise Integration Architecture: Designing for Reliability and Change
Enterprise integrations evolve constantly. This case study focuses on designing APIs, messaging, error handling, and integration boundaries that remain reliable as systems grow.
Coming SoonTechnical Insights
Concise notes on architecture trade-offs, cloud thinking, and practical engineering decisions.
Why I No Longer Wrap Entity Framework in Generic Repositories
Generic repositories promise cleaner code, but often hide Entity Framework's strengths and add unnecessary abstraction. Here's why I no longer consider them a good architectural default.
Coming SoonCQRS Does Not Require Event Sourcing
CQRS and Event Sourcing solve different problems. I explain why I frequently use CQRS in enterprise systems without introducing the complexity of Event Sourcing.
Coming SoonMicroservices Are an Organizational Decision, Not a Technical One
Successful microservices depend more on team structure, ownership, and deployment maturity than technology choices. Architecture should follow organizational reality, not industry trends.
Coming SoonHow I Approach System Design
Start with the real problem
Every system begins with the business goal, the constraints, and the change we need to enable.
Design for resilience
I focus on clear boundaries, dependable integrations, and platforms that can evolve without becoming fragile.
Make trade-offs explicit
Performance, simplicity, cost, security, and delivery speed all matter; good architecture makes those choices visible.
Planning a complex platform decision?
I’m always interested in thoughtful conversations around architecture, cloud strategy, and practical AI-enabled systems.
Start a Conversation