Tan Nguyen DuySenior Software Engineer
Based in Ho Chi Minh City • Open to impactful discussions

Crafting High-Performance Distributed Systems & Enterprise E-Commerce.

Senior Software Engineer with 5+ years of experience architecting resilient backends, migrating legacy monoliths to microservices, and delivering mission-critical platforms for global leaders like Toyota, Bosch, and Softbank.

Explore System ArchitectureGet In TouchView LinkedIn
5+Years Experience

Enterprise backend development & distributed system architecture

3+Enterprise Domains

Automotive, Enterprise E-Commerce, and Fintech Platforms

100%On-time Migration Delivery

Multi-version framework upgrades and architectural decoupling

01 // ARSENAL

Tech Arsenal & Engineering Metrics

Tools and engineering practices used to build reliable enterprise systems.

CATEGORY 01

Core Backend & Architecture

High-throughput, resilient enterprise application foundations

Java 11 / 17Spring Boot 3Spring Security 6MicroservicesDomain-Driven DesignRESTful APIs
CATEGORY 02

Enterprise E-Commerce

Scalable digital retail solutions & transactional flows

SAP Commerce CloudHybrisHeadless CommercePayment Gateways
CATEGORY 03

Data & Storage

Relational persistence, cache layers & automated migrations

PostgreSQLMSSQLOracleLiquibaseFlywayRedisCaching Strategies
CATEGORY 04

DevOps & Quality

Continuous delivery pipelines & rigorous automated verification

DockerJenkins CI/CDSonarQubeJUnitMockito
< 5%
Code SmellSonarQube gate on Bosch & enterprise pipelines
> 80%
Test CoverageJUnit / Mockito coverage on business-critical logic
02 // ARCHITECTURE & CASE STUDIES

Selected Engineering Case Studies

Architectural challenges, technical implementations, and production outcomes delivered across automotive, enterprise, and fintech domains.

CASE STUDY 01•SAI Digital

Monolith to Microservices Modernization

Client: Toyota Motor Philippines
THE CHALLENGE

The existing platform relied on a central SAP Commerce monolithic core that limited rapid independent releases and scalability. The system required greater modularity and flexibility while reducing dependency on the monolithic core and enabling a more scalable distributed architecture.

ARCHITECTURAL SUMMARY

Modernizing a mission-critical automotive sales platform running on a SAP Commerce / Hybris core by decoupling business modules into scalable, resilient microservices.

ENGINEERING APPROACH & EXECUTION
  • ▹Participated in designing and implementing independent microservices to decouple monolithic dependencies.
  • ▹Separated key functional modules to isolate domain responsibilities and allow autonomous scaling.
  • ▹Engineered reliable synchronous REST endpoints alongside asynchronous communication flows for event-driven coordination.
  • ▹Addressed distributed data integrity and eventual consistency challenges across service boundaries.
  • ▹Designed within enterprise e-commerce architectural patterns to ensure zero disruption to ongoing automotive retail transactions.
System Topology Simulator

Toggle architectural models to observe structural decoupling and state isolation.

Architecture shown is a simplified conceptual representation due to client confidentiality. Internal service names and network topologies are abstract conceptual models.
Click on any architectural node to inspect domain role, isolation semantics, and protocols.
MEASURABLE IMPACT & OUTCOME
01.Successfully established decoupled service boundaries, decreasing direct runtime dependency on the SAP Commerce core.
02.Delivered modular services enabling independent deployments and enhanced maintainability.
03.Preserved transactional data integrity across asynchronous integration paths.
TECH_STACK:Java 17Spring Boot 3SAP Commerce CloudHybrisMicroservicesDistributed Data IntegrityRESTful APIsEvent/Messaging Flows
CASE STUDY 02•Bosch Global Software Technologies

OneDriving & EET Portal

Enterprise Department & Hardware Engineering Portals
< 5%
Code Smell
> 80%
Automated Coverage
THE CHALLENGE

Legacy enterprise services built on older runtimes required modernization to contemporary LTS baselines while adhering to strict corporate security standards, centralized authentication, and automated regression guarantees.

ARCHITECTURAL SUMMARY

Modernizing enterprise backend frameworks, automating CI/CD pipelines, and establishing rigorous test automation standards for hardware project tracking and resource operations.

ENGINEERING APPROACH & EXECUTION
  • ▹Executed dual-system modernization upgrading runtimes from Java 11 to Java 17 and frameworks from Spring Boot 2 to Spring Boot 3.
  • ▹Upgraded and configured enterprise identity layer with Spring Security 6 and Azure Active Directory Single Sign-On (SSO).
  • ▹Engineered automated database migration workflows using Liquibase against PostgreSQL, standardizing reproducible schema versioning.
  • ▹Constructed Jenkins CI/CD pipelines to automate build, verification, and deployment phases, significantly accelerating release velocity.
  • ▹Treated code quality and automated testing as an integral part of the engineering workflow, backing services with JUnit and Mockito test suites.
  • ▹Enforced static analysis standards through SonarQube quality gates on every commit.
MEASURABLE IMPACT & OUTCOME
01.Achieved seamless, non-breaking upgrade across Java 17, Spring Boot 3, and Spring Security 6.
02.Maintained SonarQube Code Smell rate strictly below 5% throughout production releases.
03.Secured unit and integration test coverage exceeding 80% on critical business logic.
04.Automated schema versioning and CI/CD pipelines, removing manual deployment overhead.
TECH_STACK:Java 17Spring Boot 3Spring Security 6Azure AD SSOPostgreSQLLiquibaseJenkins CI/CDSonarQubeDockerJUnit / Mockito
CASE STUDY 03•IT Services Japan Group

Softbank Payment Service (SBPS)

Fintech & Payment Gateway Operations
THE CHALLENGE

Financial settlement flows demanded flawless execution accuracy, stringent state reconciliation, and high-performance communication between backend transaction processors and administrative interfaces.

ARCHITECTURAL SUMMARY

Developing high-reliability payment transaction processing backends and optimizing 200+ TypeScript/Angular administrative interfaces connected to core financial services.

ENGINEERING APPROACH & EXECUTION
  • ▹Engineered business logic for payment transaction processing and order request management within the Java Spring Boot backend.
  • ▹Optimized and maintained over 200 TypeScript and Angular screens connected to backend transaction services, improving responsiveness and user experience.
  • ▹Processed complex structured transaction files (YML, XML, XLSX) with strict validation routines to ensure data consistency.
  • ▹Applied object-oriented abstraction patterns to create standardized reusable business logic templates, boosting team implementation velocity.
  • ▹Mentored junior engineers and interns to ensure adherence to strict reliability standards and institutional workflows.
MEASURABLE IMPACT & OUTCOME
01.Delivered resilient transaction processing flows ensuring high data fidelity.
02.Successfully optimized 200+ screens connected to backend APIs with enhanced data loading times.
03.Achieved > 80% unit test coverage using JUnit across backend service logic.
04.Mentored 4 interns to successful probation completion within 5 months.
TECH_STACK:JavaSpring BootTransaction ProcessingPostgreSQL / OracleFlywayJUnitTypeScriptAngular
03 // TRACK RECORD

Career Journey

Progressive engineering ownership across global technology partners and enterprise clients.

Senior Software Engineer•SAI Digital
08/2024 – Present
ACTIVE
Context:Toyota Motor Philippines Project
  • ▹Leading microservices architecture and module decoupling from the SAP Commerce core.
  • ▹Designing resilient synchronous REST communication and asynchronous event-driven flows.
  • ▹Preserving distributed data integrity across independent commerce services.
Java 17Spring Boot 3SAP Commerce CloudMicroservicesEvent-Driven FlowsREST APIs
Software Engineer•Bosch Global Software Technologies
02/2023 – 2024
Context:OneDriving Portal & EET Portal
  • ▹Upgraded enterprise systems: Java 11 → Java 17, Spring Boot 2 → Spring Boot 3, and Spring Security 5 → 6.
  • ▹Integrated Azure Active Directory Single Sign-On (SSO) for corporate identity management.
  • ▹Automated CI/CD workflows using Jenkins and database versioning using Liquibase on PostgreSQL.
  • ▹Maintained SonarQube code smells below 5% and test coverage above 80% with JUnit and Mockito.
Java 17Spring Boot 3Spring Security 6Azure AD SSOPostgreSQLLiquibaseJenkinsSonarQubeDocker
Software Engineer•IT Services Japan Group
10/2020 – 01/2023
Context:Softbank Payment Service (SBPS)
  • ▹Implemented payment transaction processing business logic with high operational reliability.
  • ▹Optimized over 200 TypeScript and Angular administrative screens interfacing with backend services.
  • ▹Standardized reusable OOP component templates and achieved over 80% unit test coverage using JUnit.
  • ▹Awarded Rookie Award 2022 by IT Services Japan Group; mentored 4 interns to full completion of probation.
JavaSpring BootTransaction ProcessingJUnitFlywayTypeScriptAngular
Information Technology Engineer•Posts and Telecommunications Institute of Technology (PTIT)
2017 – 2021
Context:Engineer's Degree in Information Technology
  • ▹Rigorous foundations in computer science, distributed algorithms, data structures, and software engineering principles.
  • ▹Completed comprehensive curriculum covering object-oriented design, database theory, and networking.
Computer ScienceAlgorithmsData StructuresDatabase TheorySoftware Engineering
04 // PHILOSOPHY

Engineering Principles

Core mental models guiding distributed system design, API contracts, and operational quality.

01

Design for failure.

Network partitions, timeouts, and downstream degradations will happen. Resilient systems anticipate failure through timeouts, retries with backoff, circuit breaking, and graceful degradation.

02

Prefer explicit boundaries.

Loose coupling starts with explicit domain contracts. Clearly defined service boundaries prevent accidental coupling and maintain conceptual integrity across distributed systems.

03

Keep services independently evolvable.

Microservices exist to enable independent deployments and isolated velocity. If deploying Service A requires lockstep deployment of Service B, you have built a distributed monolith.

04

Automate quality checks.

Code quality and test coverage are not afterthought phases—they are non-negotiable pipeline gates. Static analysis and automated testing ensure architectural rules survive team scaling.

05

Treat observability and reliability as first-class concerns.

A distributed system is only as reliable as its visibility. Structured logging, tracing, and health semantics must be designed alongside business requirements, not tacked on in production.

06

Keep architecture understandable.

Sophistication is not complexity. The best enterprise architectures solve real business problems with the simplest patterns that satisfy scaling, consistency, and operational constraints.

05 // REPL RUNTIME

Interactive Shell

Execute inspection commands directly against the engineer profile context.

bash — tan@systems-core:~
SESSION_ACTIVE
Quick Run:
$tan.getCurrentFocus()
>Microservices Architecture & Monolith Decoupling
>Enterprise E-Commerce (SAP Commerce Cloud / Hybris)
>Resilient Java 17 & Spring Boot 3 Services
>High-Throughput Distributed Data Pipelines
$tan.contact()
>Email: YOUR_EMAIL_HERE
>LinkedIn: https://linkedin.com/in/tan-nguyen-duy-461b1a21b
>GitHub: https://github.com/tannguyenduy
$
06 // CONNECT

Let's Build Systems That Scale.

Whether you are architecting a high-throughput microservices platform, migrating a legacy core, or engineering mission-critical e-commerce infrastructure—let's start an impactful discussion.

LinkedInGitHub
Download Verified CV (PDF)