Bangkok, TH
UTC+7
est. 2004
UTC+7
est. 2004
About
I'm Pattapong, an enterprise architect. I treat software like architecture: load-bearing, legible, and quiet enough to live beside.
For twenty years I've designed systems for banking, insurance, and telecom: real-time data platforms, mediation and billing, machine-learning pipelines, and the cloud-native plumbing underneath. I care most about the work that doesn't announce itself - the default that was right, the failover that never paged anyone, the pipeline an operations team can actually understand. I spend as much time translating between engineers and stakeholders as I do drawing the boxes.
Principles
01
Fewer moving parts
Every component has to justify its operational cost, or it leaves.
02
Design for failure
Assume the network, the disk, and the vendor will fail. Plan accordingly.
03
Make it observable
A system you cannot measure is a system you cannot trust.
04
Decide once
A good default settles an architecture review before it starts.
Industries
BankingInsuranceTelecom
Platforms
Kafka
Spark
Hadoop
Splunk
Elasticsearch
AWS
Azure
GCP