--------------------------------------------------------------------------------------------------
Project Explanation 2026
--------------------------------------------------------------------------------------------------
Project Name (Internal):
Verizon Site Audit and Transport Fiber Logic System
Business Purpose (High-Level):
=> Verizon needed a system to automate auditing of their network sites (cell towers) and intelligently plan fiber connections.
=> The goal was to reduce manual effort by field engineers and speed up new fiber deployments.
Overall Architecture (Internal View)
API Gateway:
=> Spring Cloud Gateway (handled authentication, routing, rate limiting)
Core Microservices:
- site-audit-service
- fiber-logic-service (primary module - brain of the system)
- inventory-service
- notification-service
- reporting-service
=> site-audit-service: Ingested and validated raw audit data from field teams.
=> fiber-logic-service: Route selection for fiber connection considering distance, bandwidth, redundancy, cost, SLA, etc.
=> inventory-service: Managed physical fiber assets and port availability.
=> notification-service: Sent alerts and status updates.
=> reporting-service: Generated audit reports and analytics.
Communication:
=> Apache Kafka (event-driven, asynchronous)
Caching:
=> Redis (using Redisson client)
Database:
=> Oracle 19c (via Spring Data JPA + Hibernate)
Deployment:
=> Kubernetes cluster with Jenkins CI/CD
Deep Details of the primary module – fiber-logic-service
=> This was the brain of the system.
What I Worked On:
=> Designed and developed REST APIs for:
=> Site feasibility check
=> Fiber route calculation
=> Available port assignment
=> Bulk audit processing
=> Worked on complex business rule engine for route selection (considering distance, bandwidth, redundancy, cost, SLA, etc.).
=> Optimized the Spring Batch jobs that processed large volumes of site audit data every night.
=> Integrated with other services using Kafka (produced events after successful route assignment, consumed events from site-audit-service).
=> Used Redis extensively for caching:
=> Site master data
=> Frequently used fiber routes
=> Inventory availability
=> Implemented proper transaction management using @Transactional with appropriate isolation levels.
=> Added comprehensive logging, metrics (using Micrometer), and health checks (Spring Boot Actuator).
Major Challenge I Solved:
=> The nightly batch job was taking too long (>2 hours) and sometimes failing midway due to heavy database load.
My Solution:
=> Analyzed slow queries using Oracle execution plans.
=> Introduced Redis caching for static/master data.
=> Optimized batch logic using parallel processing with CompletableFuture where safe.
=> Reduced unnecessary database roundtrips.
=> Result: Processing time reduced from 2+ hours to ~35-45 minutes (significant improvement).
Another Challenge I Solved:
=> Race condition during concurrent fiber port assignments.
My Solution:
=> Used optimistic locking (@Version in JPA entity).
=> Proper transaction boundaries.
=> Retry mechanism with Resilience4j for transient failures.
Technologies I Used Daily:
=> Java 11
=> Spring Boot 2.7 (common in many TCS projects even in 2025-26 due to legacy codebase)
=> Spring Data JPA + Hibernate
=> Apache Kafka
=> Redis (Redisson client)
=> Oracle Database
=> Maven, Git, Jenkins
--------------------------------------------------------------------------------------------------
Talk about your projects that you worked on in TCS
=> Sure, In TCS, I majorly worked on a project called Verizon Site Audit and Transport Fiber Logic System
=> The main goal was to automate the site audits and so speed up the fiber deployments
=> I was part of the backend team and primarily worked on the fiber-logic-service module. This was the main service responsible for fiber route selection by processing the site audit data.
My Key contributions were,
=> I worked on optimizing Spring Batch Jobs that processed large volumes of site audit data every night.
=> Initially the jobs were taking around 2 hours.
=> I introduced Redis Caching for frequently used site master data, optimized several queries and added some parallel processing code in safe areas.
=> As a result, the processing time came down from 2 hours to around 45 minutes.
=> I also worked on complex business rule engine for fiber route selection, considering the parameters like distance, bandwidth, cost, etc
=> The services communicated using Apache Kafka for asynchronous events, and we used Oracle database with Spring Data JPA.
=> Overall, this project gave me good exposure to high scale backend system, rule based processing and performance optimization.
=> Apart from this, during my preparation break, I also built two personal projects payment-wallet-system and employee-management-system to strengthen my skills in Spring Boot and Distributed systems.
=> These are my recent projects experience
You were worked only one project in TCS all the 3+ years ?
=> No, That was the major project, where I worked for more than 2 years
=> In that project, I was initially in development, then in optimization, and later in supporting production issue fixes.
=> Before that, I worked on different project for the same client, where I handled few new requirements, bug fixes, Sonar and Fortify issue fixes. There, I also got a chance to handle some frontend tasks involving ReactJS.