Somehow the “CMDB Industry” keeps me wondering. To set up a CMDB correctly, so that it provides the right information at an acceptable cost, is very hard to do. So why should “federating” (**buzzword alarm**) information make things easier? So what is this federating?
Federation allows you to setup a connection from your CMDB to any other data source and to use that data in your CMDB without importing it. Sounds hip, but why should you do this? Will it:
- Save you money? No, the cost of data is in managing the data and it’s consistency, not in the storage space.
- Save you development time? No, the difficult part in your CMDB design is still getting all the information into one data model, so that does not change with federation capabilities. Quote from the CMDBf Vision Paper: “4.3 A common data model is essential for successful federation of data from multiple MDRs.“
- Give you a new exciting capability? Eehm, no not really. The current CMDBs allows you to federate attributes only. This is the most “dull” type of information in a CMDB (CIs and their relationships are much more interesting).
So why should we federate CMDBs? Beats me.
Start thinking about your process!