Back to Forum

CI/CD pipelines for small Malaysian engineering teams — what actually works

by Winston Teo·May 23, 2026

We're a team of 6 engineers at a Malaysian fintech. Here's what our CI/CD setup looks like after two years of iteration.

What we use:
- GitHub Actions for CI (free tier covers most of our needs)
- Docker for containerisation
- AWS ECR + ECS for deployment
- Terraform for infrastructure as code

What we dropped:
- Jenkins: too much overhead to maintain for a small team
- CircleCI: pricing changed in a way that made it less attractive than GitHub Actions

For those just starting:
GitHub Actions + a simple deployment to a single cloud server (EC2, DigitalOcean Droplet, or even Railway) is a perfectly valid starting point. You don't need Kubernetes until you have scaling problems you can actually measure.

Malaysian-specific note: AWS ap-southeast-1 (Singapore) is the default region for most Malaysian companies. Latency is good and the region has full service availability.

#CI-CD#DevOps#AWS#GitHub-Actions#engineering
198 upvotes6 comments

Comments (6)

Zainol Ariff17

Agile retrospectives only work if the team feels safe enough to say what actually went wrong. If retros are only positive, the culture has a problem.

Belinda Cheong20

The daily standup that turns into a 45-minute meeting is not a standup. Three questions: what did you do, what will you do, what blocks you. Timebox it.

Hafiz Zuhairi9

Kanban vs Scrum: use Kanban for support/ops work where priorities shift constantly. Use Scrum for product development with defined sprints. Match the tool to the work.