8 static endpoints
Profile, projects, metrics, insights, styles, feed, search, and OpenAPI are generated at build time.
Backend & Platform Engineer · Tainan, Taiwan
Backend and platform engineer connecting event-driven research, production delivery, and home-lab operations.
Reliable services after the demo About
I am a software engineer and service developer with an M.S. and B.S. in Computer Science and Engineering from National Taiwan Ocean University. My strongest through-line is reliability: service design, event flow validation, deployment, and operations.
At SOSELAB, my thesis work became CCTS, a Composite Contract Testing Service for event-driven microservices. It combines Pact contracts, runtime event logs, and state-model validation so testers can detect missing transitions and execution failures instead of trusting happy-path demos.
At ITRI, I worked on the Personal Data Authorization System and a personal-data valuation/payment platform. The work touched logging, payment, blockchain, third-party fintech, CI/CD, infrastructure, and delivery on Azure Kubernetes Service.
Outside formal roles, I run a home-lab with 30+ services across storage, DNS, monitoring, media, albums, and home automation. That environment keeps my platform work honest because I live with the operational consequences.
Education
National Taiwan Ocean University (NTOU) · Graduated 2016 - 2022
Thesis focus: Event-driven microservices architecture and testing methodology
Publications · IEEE
Chu-Fei Wu, Shang-Pin Ma, An-Chi Shau, Hang-Wei Yeh
Introduces CCTS (Composite Contract Testing Service), a testing tool for event-driven microservices. Combines consumer-driven contract testing with event-driven state models to record state transitions of event exchange between services and automatically retrieve possible transition paths.
First author · thesis work
IEEE · ICS 2020 — International Computer Symposium · 2020 · Tainan, TaiwanYu-Te Wang, Chu-Fei Wu, Shang-Pin Ma, Hsuan-Tung Chen, Shih-Ying Chang, ChunSheng Li
Uses Citizen Digital Certificate, digital signature, and blockchain to establish an authorization system (PDAS) for digital personal data. Enables safe, undeniable, and tamper-proof data authorization contracts that address legality, security, and multi-user authorization.
Co-author · PDAS-team core contributor
Conference Papers · Domestic
Awards
2022 台灣軟體工程研討會 (TCSE) — for "事件驅動微服務系統之複合契約測試機制"
Research Highlights
Metrics
Stack
Projects
Composite Contract Testing Service — my NTOU thesis system and APSEC 2022 paper implementation. It combines Pact contracts, event-log sequence validation, and state-model checks to catch missing transitions and execution failures in event-driven microservices.
Java · Spring Boot · Docker · Fly.ioAnonymous Discord reply bot built for the NTOU CS Discord context. It grew from a course project into a containerized service with CI/CD, Docker Hub image flow, and Fly.io deployment.
Docker · Linux · NAS · MariaDB · SDNHome-lab service configuration and operations notes. The broader environment runs 30+ services across storage, DNS, monitoring, media, albums, and home automation with VM/container integration.
Shell · Docker · IPMI · ESXi · NVIDIADell PowerEdge fan control through iDRAC/IPMI with Docker deployment, NVMe/GPU temperature inputs, configurable thresholds, and a recent README/code audit around fail-safe behavior.
Experience
Designed and implemented CCTS — a contract-testing framework for event-driven microservice systems. Published at IEEE APSEC 2022, received the 2022 TCSE Best Chinese Paper Award, and maintained related PoC services for orchestrator/payment/points/logging flows.
Researched, designed, implemented, and delivered personal-data authorization and valuation/payment systems. Worked across decentralized architecture, microservices, event-driven design, CI/CD, security, blockchain, third-party finance, AKS deployment, and delivery documentation.
Maintains and modernizes digital systems for CNC manufacturing workflows, moving legacy products toward more reliable internal architecture while targeting high availability.
Helped migrate legacy course content into a newer content-management workflow and supported professors with lesson design and assigned customization.
Contribute across personal infrastructure, team projects, and public OSS workflows. Pattern: cleanup, integration, correctness.
Open Source
Role Fit
Service delivery with microservice, event-driven, API, messaging, and persistence experience
Deployment-aware engineering across containers, Linux, storage, network, and operational automation
Practical architecture decisions under research, customer-delivery, and public collaboration constraints
First 90 Days
Beyond Code
I build systems that stay standing after the demo. Let's connect.
Portfolio intelligence layer
This shared layer turns every variant into a richer portfolio surface: API endpoints, command search, live GitHub enrichment, article cards, timeline context, and machine-readable data.
Profile, projects, metrics, insights, styles, feed, search, and OpenAPI are generated at build time.
The client can fetch current public profile data without requiring secrets. If the network fails, static evidence remains complete.
Ming-Chyuan MIS work creates a long-running baseline: software has to survive legacy systems, manufacturing workflows, and maintenance pressure.
B.S. and M.S. work converge on service-oriented architecture, event-driven testing, and maintainability under research constraints.
CCTS turns consumer-driven contracts, event logs, and state models into a composite test service for event-driven microservices.
Personal-data authorization and valuation/payment platform work spans logging, payment, blockchain, CI/CD, fintech integration, and AKS delivery.
Self-hosted systems, server automation, and public PRs keep the engineering habit grounded in operational feedback.
Engineering journal
CCTS matters because it connects contract definitions with event-log paths and state-model assertions, closing the gap between interface agreement and actual behavior.
The PDAS work shows why deployment, CI/CD notes, infrastructure constraints, and customer handoff are not afterthoughts; they decide whether the system can be trusted.
Running storage, DNS, monitoring, media, albums, and automation changes how architecture feels: failures become personal, and clarity becomes operational leverage.
Integration, localization, and documentation fixes reveal a practical collaboration style: learn the boundary, reduce friction, and leave a clearer path behind.