Editor’s Note: One of the paramount challenges of maintaining a relatively large codebase as it continues to grow is architecturing a well-planned code organization with foresight and self-certainty early on. Bobby Priambodo witnessed such a streamlined codebase landscape when he joined Traveloka and today, he would like to share in detail his views having had experiences in interfacing with an instance of the Java- or Kotlin-based backend services in creating numerous benefits particularly for testing.
Bobby Priambodo is a lead software engineer overseeing the engineering efforts for both the Accommodation product’s Search team and the Engineering Quality team. …
Imagine if Traveloka worked like a supermarket that had only one cashier, and we handled our customers one by one. There would be a very long queue, and even the 5th customer would probably leave as soon as she felt that it was taking too long. She would then go to another supermarket. We wouldn’t want that.
This article is part of Hands-on OCaml, a series of articles that I’m working on that is focusing on doing web app development with OCaml.
The project we will be building throughout the series is a To-Do List app, which connects to a PostgreSQL database as its datastore. In the previous article, we have covered initializing and bootstrapping our project with Dune; if you haven’t seen it, check out the link below:
This tutorial will build upon the foundation we have laid out in the previous article in the series. While you can of course follow along without actually doing the tutorial, it is recommended to give the article a read first to be sure that we have the required knowledge in place. …