Visualized by Ilyas Fahreza

Editor’s Note:

Fatih took over the baton from the preceding article on Traveloka’s web performance culture (penned by Ryan Nixon Salim) to share with us today the accompanying technical optimization techniques governing Traveloka’s site that you can utilize as an implementation reference taking into account the nature of distinct constraints that individual environment has.

Fatih Kalifa is a web infrastructure software engineer, whose responsibilities include developing web framework, improving web performance, as well as collaborating with the design team to enhance system design, tooling, & workflows.

In the previous article, we’ve discussed how we built a performance culture in Traveloka…


This is a story of our soon-to-be-deprecated JS framework used in Traveloka mobile web. No, this is not a sad story, but rather a journey full of insight and learning along the way.

The story began at early 2015, when we decided to write our own server-side rendered, single page application JavaScript framework.

Why?

You might be wondering why we decided to build our own JS framework.

Remember, that was early 2015, where Angular was still gaining traction, jQuery was popular as ever, and React? Well, let’s just say people still couldn’t get over HTML-in-JS.

https://trends.google.com/trends/explore?date=2014-07-01%202015-03-31&q=%2Fm%2F0j45p7w,%2Fm%2F012l1vxv,%2Fm%2F0268gyp

Frontend engineering was still relatively quiet…

Fatih Kalifa

Interface Engineer. https://fatihkalifa.com. Medium is used to write for publication only. Currently: Traveloka Engineering

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store