Service Design Guidelines

Guidelines

 

 

ü 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 strategy for  Adaptor services and Versioning in Business Services ü Try to minimize the business logic and persistence in Integration Layer . ü All the Business services should be captured in Service Catalogue ü Business Services Should be Coarse grained ü Process and Adaptor services may be coarse grained or fine grained ü  Try to implement the Cache as much as possible for those read operation ü Environment related information should not bundle with service package , it should be externalize ü Service Name should Noun and Operation name should be Verb . ü Try to implement the Pagination for critical/bulk read operation to prevent the resource utilization