Contracts Are Only Useful When They Meet Runtime Evidence
CCTS matters because it connects contract definitions with event-log paths and state-model assertions, closing the gap between interface agreement and actual behavior.
吳朱飛 / Backend & Platform Engineer
Backend and platform engineer connecting event-driven research, production delivery, and home-lab operations.
Featured essays
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.
Publication shelf
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 / 2020Uses 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 contributorComposite Contract Testing for Event-Driven Microservice Systems
最佳中文論文獎 · Best Chinese Paper AwardPricing and Bidirectional Payment Platform for Digital Personal Data Authorization
Design of a Digital-Signature-Based Personal Data Authorization Platform
Chronology
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.
Behind the page
Everything on this site is also machine-readable: static JSON endpoints, a searchable index (Ctrl / ⌘ + K), and a live GitHub lookup that degrades gracefully offline.
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.