All new request for allowing connection to CNTRES Service won't be approved anymore, effective from August 9th, 2021, unless there's a strong justification.
Existing CNTRES Client will remain untouched and will be gradually migrated with the help from Content Team.
All new integration should use the new content resource library.

Background

As we know it, Content Resource Service building block help centralized localization effort in Traveloka by providing localized text, image, and commerce template to be consumed by other products in Traveloka. As Traveloka system grows and evolved throughout the past couple years, there are a couple issues arise and need to be addressed. This new Content Resource Library is created to fix that problem.

Scalability

Content resource architecture no longer able to keep up with the growing number of products and services. With the old architecture, the platform will hit the limit of allowed connection with another 100 new services with the way it is currently designed. Our new architecture removing that limit, allowing as many as product services to read Content Resource by only adding single line of policy to S3.

Reliability

System have proven to be unreliable and if we try to focus on increasing its reliability, the options are more towards increasing number of instances both for server and database, but it’s still exposing the risk of Single Point of Failure and more costly compared to if we try to design a whole new infra suited for static content use case. Our new architecture removing that Single Point of Failure (especially the database), allowing our client to read the CR value directly from much more reliable source (S3), with cache in place to preserve the low-latency access.

Operational Cost

Operational is costly, need to do load test for planned traffic increase and then increase the number of EC2 every high event traffic. Our new architecture removing this effectively by moving the traffic from RPC to S3 directly, eliminating the need for scaling the service machine, since the traffic is directly served by S3 and client server machine.

:safety_vest: Is it safe to migrate?

We can say confidently, yes, it's safe to migrate.
Up until now, 80% of CNTRES Traffic (~17mio Req/day) has been migrated to the new system and there's no noticeable negative impact on reliability and latency.

:calendar-icon: When will the CNTRES be fully deprecated?

We're planning to fully deprecate the CNTRES service on ~~December 31st, 2021 at the latest~~. Pushed to End of Q1 2022

What does it mean for existing CNTRES Client?

Existing CNTRES Client that already has a connection to CNTRES will remain untouched and can still use CNTRES Service.
If the service is being migrated to multi-account, the service should integrate with new system on the new account.
Content Team will gradually contacting each team that use CNTRES and helping them to adjust their codebase using the new library.
But if you want to migrate it yourself, we'll be more than happy to let you to do it :bows: . You can follow the guide for migrating to the new library.

What does it mean for new CNTRES Client?

New CNTRES Client, which have no existing connection to CNTRES or being migrated to multi account, is required to use our new content resource library and integrate with the new system from now on.
Kindly follow our new integration guide for new integration request.

Should you have any further question regarding this, please don't hesitate to raise it at #content-channel
Thank You All!

CNTRES Migration and Deprecation

TL;DR