Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
.net android asp.net asp.net mvc azure backup bigdata book c# community continuous delivery database denali functions gotcha how to howto indexing java linq mongodb nancy nhibernate nosql performance powershell restore ruby security silverlight sql sql advent 2012 sql friday sql server sql server 2000 sql server 2005 sql server 2008 sql server 2008 r2 sql server 2012 sql server denali sqlcop ssis ssms structuremap t-sql tip unit testing vb.net visual studio 2010 windows 7
- SQLDenis (576)
- Christiaan Baes (chrissie1) (527)
- Ted Krueger (onpnt) (332)
- Jes Schultz Borland (grrlgeek) (139)
- Eli Weinstock-Herman (tarwn) (116)
- Alex Ullrich (51)
- George Mastros (gmmastros) (46)
- Naomi Nosonovsky (27)
- Axel Achten (axel8s) (23)
- David Forck (thirster42) (22)
- Koen Verbeeck (20)
- Kevin Conan (18)
- chopstik (18)
- Rob Earl (14)
- thatrickguy (12)
I thought I would share a recent question that was raised on LinkedIn, which asked: Starting the Holy Wars on ESB? Who brings the best package deal to the table i.e IBM, MSFT...... Look at this way " A mid sized cash crunched has to implement ESB w…
So what is a CDM ?…
A Canonical Data Model is most simply explained as a standardised way of representing data that generically applies to multiple systems and data models - kind of like the master data model, but for semantics aswell as content. It can be used as a data model standard template for new systems development, or as an intermediary serialised data format - which is the aspect I’ll focus on mostly here.
Here’s an Example of using the CDM as an intermediary data format to integrate six systems with different data format requirements: Canonica...