CMDB application dependency layout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2016 11:39 AM
I am currently building a CMDB primarily focused on assets in the form of application services. As far as the structure is concerned, I am struggling with determining how the application service and its dependencies should be laid out. Currently, I have this structure set up in my CMDB:
Business Service (tier 0)
|
Application Service (tier 1)
|
Application Server (tier 2)
|
Database Server (tier 3)
|
Database Instance (tier 4)
I am fairly certain that this is the correct way to build as CMBD as far as actual systems hierarchy is concerned, but is this the best way to do it as far as accessibility and maintaining it for the future goes? I have seen some examples with tiers 2, 3, and 4 all clustered on tier 2, but it seems that this way would model the actual relationship the best. Any input on whether or not this layout could work well with applications and maintenance would be appreciated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2016 03:35 AM
Dustin:
This is a great topic for discussion, and comes up often when I am teaching. I thought I would pass along some of things I have developed over the last five years on this topic. Here is the article that I published yesterday.
Pragmatic Patterns — Basic Business Service Management Patterns
Steven Bell