About / Blogdoang

Cloud, simply

Blogdoang is the cloud architecture, DevOps and app development practice of Abdul Aziz, and the field notes that come out of it.

The work is cloud architecture, migration and DevOps: platforms on Google Cloud, AWS and Azure, moved between them without downtime, codified in Terraform and Ansible, and secured with zero trust, WAF and SIEM to meet standards such as PCI DSS. It also covers the apps on top: web apps on FastAPI and Laravel, and native Android apps such as Miauw, a music player for phone, car and TV.

blog·doang
noun · from Jakarta slang
1 “Just a blog”: doang means “just” or “only”. It started as a place to write fixes down.
2 A practice for cloud platforms and the apps on them, built step by step and written down.
Fig. 1 · The name, defined.

Behind Blogdoang

The person who writes the notes and builds the platforms.

Abdul Aziz

Cloud architect, DevOps engineer and app developer. The work has grown from running servers, mail and networks to designing and migrating multi-cloud platforms for product companies and enterprise clients, and building the web and mobile apps that run on them.

Every note on this site began as a real problem and ends with a command that proves the fix works. Video walkthroughs are on GCP Daemon.

Case studies Get in touch
Role
Cloud architect, DevOps engineer, app developer
Experience
10+ years in infrastructure
Clouds
Google Cloud · AWS · Azure · Alibaba Cloud
Apps
Web · Android phone, Auto and TV
Based
Indonesia · working remotely
Elsewhere
GitHub LinkedIn YouTube

Method

The same four steps behind every project and every note.

Name it, draw it, run it, prove it.

  1. Step 01

    Name it

    Start from the real situation: what runs today, where it hurts, and what “done” looks like.

  2. Step 02

    Draw it

    Sketch the path a request, a packet or a deploy takes, before touching a console.

  3. Step 03

    Run it

    Change one thing at a time, in code (Terraform, Ansible, CI), so every step can be repeated.

  4. Step 04

    Prove it

    Finish with a check that shows it works, then write it down as a runbook.

Credentials

Each one links to its public verification page.

Checked by someone else.