As preparation for surviving Lebaran 2017, TERA is implementing rate limiter to prevent the transactional service from being overloaded by requests.
Please note that rate limiter is a self-defense mechanism of the server. The clients who are rate limited should have their own fault-tolerance mechanism.
Rate Limiter can limit based on certain time window, the client app, and resources called. Note the limit is per machine
Rate Limiter Config
At this point, we already put rate limit on these endpoint.
/search/searchHotelInventories
/search/searchHotelRoomInventories
/search/searchHotelRoomInventory
/book/bookHotel
/book/issueHotel
/book/checkHotel : TAP verifies issuance status
/book/cancelIssuedHotel : TAP fetches cancel-related info (refund amount, etc)
/book/cancelIssuedHotelConfirm : TAP confirms the cancellation
The limit is set to be 5 times peak request, within 5 minutes
If your application is getting 429 http status code due to Rate Limiter, please let TERA Team (@tera-eng) know. We are currently setting huge global Rate Limiter (1 million calls per 5 minutes)
Metrics monitoring can be seen here: https://metrics.traveloka.com/dashboard/db/hdemand-app-servers
Thanks,