Posts

Showing posts from May, 2017

Architecture Principles

Start With Services Virtualize Your Application Services Control Service Access by Policy Adapt to the Blurred Application Boundaries Protect Data Integrity Through Privileged Data Services Think Cloud When Designing Back-End Application Services Think Mobile When Designing User-Facing Front-End Software Design Your Data Model With the CAP Theorem in Mind Use Separation of Concerns to Foster Agility, Efficiency and Resilience Use Event Processing in the Eventful World Automate Context Discovery Use In-Memory Data Grids and DBMS (edited)

Business Decompostion into Service

We can Identify the Business Capability in following ways 1) Organization Structure - Work with differnt groups of Peoples to understand business functional ,Business Process and etc 2) High level Domain Model - Based on the High level Domain Model also we can understand basic business functionality How to Decompose those Business Capability into Services

Coupling VS Cohension

Cohesion Coupling Cohesion   is the indication of the relationship within   module . Coupling   is the indication of the relationships between modules. Cohesion shows the module’s relative   functional   strength. Coupling shows the relative independence   among the modules. Cohesion is a degree (quality) to which a component / module focuses on the single   thing. Coupling is a degree to which a component / module is connected to the other   modules. While designing you should strive for   high cohesion   i.e. a cohesive component/ module focus on a single task (i.e.,   single-mindedness ) with little interaction with other modules of the system. While designing you should strive for   low coupling   i.e.   dependency   between modules should be less. Cohesion is the kind of natural extension of data hiding for example,   class having all members visible with a package having default visibility. Maki...