These transition patterns typically involve a two- However, reliance on legacy systems, cost step process, i.e. starting with an existing MDM of maintaining such systems and the data implementation, integrating with a data lake and synchronization requirements needed to eventually migrating all hubs and capabilities to enable the successful transition to the new the data lake. Some organizations bite the bullet Digital Master are some issues to contend with. and go for this end state directly. In the “Extend” strategy, clients opt to keep the traditional master With a “Replace” strategy, clients have an in the existing traditional integration hub while opportunity to build a robust new Digital extending or expanding the capabilities beyond Master entirely around a big data lake. This is a the traditional ones by integrating with a data lake. significant emerging trend, especially with data lakes becoming more mainstream in the digital The information hub is typically decoupled era. Clients can leverage existing data lakes with from the integration hub, which helps in scaling the added flexibility and freedom of building and maintenance, but also in complexity and adaptive intelligent master data models. operations. The reduced time frames for the project build and deployment are an added Other pros of this approach include a more incentive to achieving a minimum viable product seamless coupling of the various logical hubs as quickly as possible. Table 3 on the following and reuse of common services. The cost of page shows the pros and cons of these building from scratch, time to deploy and data transition strategies. lake immaturity are all possible challenges. Meet Your Digital Master 37