A Thought Experiment Showing the Value of Separating the Business and Technical Catalogs
By B R Clouse-Oracle on Jun 18, 2014
One common error when creating a business catalog is to expose the underlying technologies that should be mentioned only in the technical catalog. For IT professionals whose day-to-day lingo is based on products and features, this is an understandable mistake. And from their perspective, perhaps not at all noteworthy.
Imagine a large enterprise's business catalog which covers all the different types of workloads and storage models the enterprise deploys - OLTP, Data Warehouse, batch and real-time analytics, structured and semi-structured data -- so far so good. Now suppose that the business catalog exposes the database and analytic engines delivering each type of data source. This might look OK if the expected vendors and products appear in the appropriate slots. But what happens when a vendor takes a big leap forward and is now the new best choice to deliver a given service? Once IT is ready to make that shift in their delivery model, they will need to update the business catalog accordingly. This is typically not the kind of the change consumers are eager to see. Instead, they should only see the lower costs and higher SLAs that IT can now provide - without being led to worry about the changes behind the scenes.
This is exactly the scenario that a product-centric business catalog might be facing soon, thanks to some upcoming releases at Oracle, namely, Oracle Database In-Memory and the Big Data Breakthrough. And the innovation won't end there. So make sure your business catalog takes the future in to account with the right structure (and of course the right products to support the business services!)