Posts

Showing posts from October, 2017

Service Design Guidelines - SOA

Business Services should be Stateless Services should be reusable Standardize the interface contract , Should expose in CDM Each Business Services will expose as 1 or 2 Proxy Services Consumer not ready to adopt our business/Proxy services due to data format then will define the Adaptor Services for those consumer only Aggregation should be in Process Services/Adaptor services ie Process Service/Adaptor Services will aggregate more than one business services NFRS should be in Cross Cutting Manner , we can enable/disable without /minor changes in services level ESB will trigger the alert if any unknown exception or services down Communication between our Business services and Provider System always through enabler Services(Data Services) . Define the Throttling /rating in Service and Operation plus consumer level Security (authentication and authorization ) should be in place Try to implement the versioning in the business service to prevent the redundancy Define the strat...

CDM-Canonical Data Model

What is CDM? What is CDM? CDM is the abbreviated form of "Common Data Model" or "Canonical Data Model". CDM is intended to be a common vocabulary for data at the enterprise level. (How is this different from EDD?) When do we use CDM? CDM should be used in the following scenarios: Integrate more than two systems Integrate with in two Systems if more frequent changes in those Systems Entities which are in CDM will reuse in many place in Enterprise level Where is CDM used? CDM mainly used in Integration Layer Values & Principles CDM Should be built rather than COTS Try to create only one CDM in EAI level instead of maintaining too many CDM Easily understood by all the users not only technical folks Review and update more frequently Re-usability Extensible Drafting Notes CDM a Common Vocabulary for Data in the Enterprise level Try to create only one CDM in EAI level instead of maintaining too many CDM. CDM Should ...