Backend systems
Go · Node.js · REST · gRPC · Distributed services · Concurrency
Backend · Platform · Reliability
Taufik Triantono
Building reliable backend systems and exploring cloud platform engineering.
Backend engineer with 8+ years of professional experience building and operating production systems across fintech, loyalty, SaaS, and agritech. I work primarily with Go, PostgreSQL, distributed systems, observability, and cloud infrastructure.
01 / About
Learning by building systems that have to work.
I entered software engineering through a vocational background in computer and network engineering, then continued learning independently through professional work, experimentation, and personal projects.
My experience has been primarily backend engineering, but over time my interests have expanded toward distributed systems, reliability, observability, cloud infrastructure, and platform engineering.
I enjoy understanding not only how an application works, but also how it behaves after deployment: how it scales, fails, recovers, is monitored, and how infrastructure costs can be understood and controlled.
02 / Engineering interests
The systems around the application.
Areas I work with and continue to explore—not a list of expert-level claims.
Data
PostgreSQL · MongoDB · Redis · ClickHouse · Transactions · Consistency
Messaging
Kafka · Asynchronous processing · Event-driven systems
Platform
Docker · Kubernetes · GKE · Nomad · GitLab CI/CD · GitHub Actions
Observability
Prometheus · Grafana · Jaeger · OpenTelemetry · Tempo
Cloud
Google Cloud Platform · Compute · Networking · Deployment · Infrastructure experiments
03 / Selected work
Projects as engineering laboratories.
Personal, open-source experiments for understanding difficult backend and infrastructure problems in depth.
01Open-source billing experiment
Billing
A personal open-source billing platform experiment focused on understanding the internals of usage-based billing systems.
Products & pricesSubscriptionsUsage ratingBilling cyclesInvoice generationIAMResource monitoringMulti-tenancy
02API design experiment
Railzway APIs
A personal contract-first API experiment for exploring how public billing and payment interfaces can remain consistent, versioned, and implementation-independent.
01Proto contract→
02Buf validation→
03Generated SDK→
04gRPC service→
05REST gateway→
06API consumer
“How can a financial API evolve without weakening its domain invariants or breaking existing consumers?”
Contract-first designResource-oriented APIsAPI versioninggRPC transcodingBreaking-change detectionIdempotency semanticsFinancial invariantsGenerated SDKs
03Go service toolkit and workspace CLI
Macro
A lightweight Go toolkit for scaffolding consistent services, workers, and jobs, organizing them in workspaces, and standardizing runtime infrastructure without coupling business logic to the framework.
01Workspace manifest→
02Project scaffold→
03Composition root→
04Application service→
05Infrastructure adapter
“How can Go projects share reliable structure and infrastructure conventions while keeping application logic independent?”
Project scaffoldingWorkspace managementTyped manifestsService lifecycleWorker lifecycleGraceful shutdowngRPC transportpprof diagnosticsCross-platform releases
04 / How I think about engineering
Calm systems come from
deliberate decisions.
- 01
Systems should be observable before they become difficult to debug.
- 02
Business boundaries and infrastructure boundaries do not always need to be identical.
- 03
A service should be testable independently where practical.
- 04
Operational complexity should be justified by a real requirement.
- 05
Infrastructure changes should be measurable and reversible.
- 06
Prefer explicit state transitions over generic status updates.
05 / Experience
Professional experience.
More than eight years building and operating production backend systems.
Sep 2020 — Present
Backend Engineer
Ottodigital Group · Indonesia
Building and operating backend systems for loyalty and reward processing, with a focus on reliability, data consistency, and maintainable service boundaries.
- Diagnosed race conditions and distributed consistency issues across Kafka event streams and Redis caching layers.
- Introduced stricter timeout and lifecycle management with Go context to reduce goroutine leaks and cascading failures.
- Refactored legacy shared services and replaced database-driven cron scheduling with in-memory backoff and retry mechanisms.
- Maintained core loyalty-point and third-party voucher aggregation systems with an emphasis on data integrity and secure reward processing.
Apr 2019 — Apr 2020 · Jul 2017 — Dec 2018
Backend Engineer
8Villages · Jakarta, Indonesia
Worked on backend APIs, cloud integrations, payment connectivity, and data products for community and agricultural platforms.
- Built and maintained concurrent REST APIs for a content-sharing community platform.
- Migrated static assets to Google Cloud Storage and introduced centralized production logging and monitoring with Google Stackdriver.
- Built FinPay payment connectivity and billing synchronization with Telkomsel systems.
- Built and maintained a farmer dashboard providing localized agricultural information.
Education
SMK Swasta Bina Mandiri
Vocational High School in Computer and Network Engineering (Teknik Komputer dan Jaringan)
Graduated 2013Languages
Bahasa IndonesiaNative
EnglishWorking proficiency
06 / Contact
Let's talk about backend systems,
platforms, and reliability.
If you are working on thoughtful infrastructure or backend problems, I would be glad to hear about them.