We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

信的彩的网的登陆网址,e 的彩

Noam Tamarkin

Standards for data model in web service

信的彩的网的登陆网址,e 的彩,无极4娱乐,彩客网彩票官网足尖史馆没事了

Hello to the service designer,

In most SOA projects the main question is about how to model the data.

It is clear that the best model is canonical model that will represent each entity in a single way.

It is very popular to comply with some standard. For example UBL, eTOM/SID etc.

It also sounds correct to go with a global standard.

I would like to analyze pro's and con's for using a global standard for data modeling.


1. Benefit from the experience of many others
2. Best for B2B (when all other partners will implement it as well)
3. Good for your reputation in the company. Managers love global standards


1. Will never be sufficient and will require local enhancements
2. Requires adaptation by applications OR intensive integration work of data transformation
3. All teams must be educated on the standard and commit to it
4. Continuous alignment of the model to the standard's new versions. 
    Conflict with local enhancements (1)

My interpretation
Always look to your assets. Look to what data models your organization already have.

If applications people understand each other in integration discussions.
If business people understands the data model.
If data transformation in your ESB is minimal and kept only to less than 30% of payload.
If the above fit your organization, maybe you already have a canonical data model !!!
In this case, try to build your data model based on existing entities, terminology and functionality.

It may not be global but it will fit your organization like a glove!

Hope I raised some eyebrows.

Leave a comment

In this blog, Noam Tamarkin provides ideas for improving and better integrating your applications.

Noam Tamarkin

Senior software architect and CTO. Experience in solution design and implementation. Holds the ability to understand complex business processes and translate them to technology. Expert in Enterprise applications, integration, SOA, SaaS. Experienced in project management, technical infrastructure, procurement and manufacturing.


Recently Commented On

Monthly Archives