Team trpdata will be decommissioning view-mongod which is shared legacy database by the end of Q3. The current remaining collection in the db is AgentBookingView, which is a view data structure of AgentBooking that contains product booking information). Furthermore, view-mongod is a shared infrastructure used by multiple products which resulting as a single point of failure.

Why is this important?

It is a shared database used by multiple services from different tiers along with different usage patterns. An example is you would not want your issuance process to fail just because some other product tools is running a long query.
Since AgentBookingView is replicate of AgentBooking (found in fb-mongod) with both having different infrastructure, information integrity issue could occur. It could happen when an anomalies occur because the data consistency in view-mongod are manually being forced (eventually consistent). Thus, this could cause problems in transactional activities such as issuance and operation related tools where state found in AgentBooking might differ with AgentBookingView.
Abstraction issue where a single view data structure could not scale well if we are trying to store multiple product specific context in a single data structure.
This is a blocker for multi-account migration where you could not add a new connectivity to a legacy database.

How can I migrate?

You will need to remove AgentBookingViewService usage or dependency from your service(s). In order to do so you can find decoupling guide in AgentBookingViewService’s java docs.
As for reference here is a spreadsheet containing list of usages that we have identified along its proposed solution although some solution might differ during the actual implementation. Kindly check whether your team are impacted or not.

When Is The Time Limit?

View-mongod will be decomissioned by September 30th 2019. Please ensure your use case(s) has been migrated before then. Failing to migrate before the timeline will cause your system to lose access to view-mongod

Should you have any questions, please feel free to reach @tripdata-eng in our slack channel #user-eng-channel.

Decommission Notice: view-mongod

Decommission Notice: view-mongod

Background

Why is this important?

How can I migrate?

When Is The Time Limit?