Grant connectivity from hotelasset-mongod and acontent-mongod consumers to aprhd-lbint

h1. Request Details
h2. Background
In order to decouple and transform our current system towards microservices, aprhd-app will own hotel data thus direct access to acontent-mongod and hotelasset-mongod will be from aprhd-app. After this cluster is live, we will revoke connectivity from other services to acontent-mongod. Currently, some of hotel data is handled by ne, a legacy service that has become a single point of failure especially for hotel products. While others access directly to acontent-mongod or hotelasset-mongod to get hotel related data. In previous ticket to create aprhd cluster, there’re still some missing connectivity from clients to aprhd-lbint to replace access to database.
h2. Purpose

To have a dedicated services that own hotel data
There’s no direct access to acontent-mongod and hotelasset-mongod except from aprhd-app

h2. Impact
By separating hotel data to aprhd-cluster, we will have a dedicated service that will own hotel data. By having a single responsible service, we will be able to improve hotel data retrieval or update easily. We can properly monitor and manage each client services request and derisk acontent-mongod and hotelasset-mongod from unwanted increase in number of requests from one of the clients.
h2. Risk

Increase network latency from clients to get hotel data as previously client will call directly to database. After changing access to aprhd, there’ll be extra latency from clients to aprhd-app that will retrieve data from database.

But the increase in latency will not be significant enough.

h2. Resources
h3. Connectivity
h4. Rules
[^connectivity.csv]