How the adoption of event-driven architecture helped GOJEK streamline ingestion of merchant data for its products.

The story of GOJEK’s Tile38-based serviceability solution which helped improve efficiency and code maintainability.

We built a tool to help us monitor GOJEK’s substantial GCP infrastructure. Then we open-sourced it.

How to set up and use Espresso — Google’s instrumentation testing framework for Android.

A guide to deploying GOJEK’s open-source reverse proxy to Kubernetes and using it to shard incoming requests.

How the GO-LIFE iOS team reduces dependencies on the backend team during development.

Dispelling common misconceptions about testing and the people who perform it.

The story of our investigation into unprompted Consul ‘watch’ triggers, and what we learned in the process.

Introducing GOJEK’s news aggregator GO-NEWS — our first product built in collaboration with a third party.

A collection of thoughts and resources to help you get better at Android development.

A deep dive into the inner workings of Watches in Consul.

.

The methods we use to help our customers find what they want in the GOJEK app.

By Jenson CS Building scalable and maintainable infrastructure is a complex problem when you have 18+ products. We have around 500+ microservices provisioned on Google Cloud Platform (GCP), Amazon Web Services (AWS), and our own data centers. We started with a single Google project called gojek-production and deployed all our

Table tests are well and good, but have you heard of the golden file?