Aggregated Core Services


		Aggregated Core Services Aggregated Core Services is extensions to Core Services. ACS is usually either context-specializing (CustomerCustomer and VendorCustomer) or aggregations from several Core Services like in CustomerDashboard which aggregates from Customer Service, Order Service and possibly more services


Characteristics Services combined and orchestrated to produce aggregated services - Aggregated functionality from several services - Context mapping - Translating between contexts - Anti corruption layer - No central persistence - Could (should) have cache (state full) Code-Patterns for Aggregated Core Services - Evolving Service Endpoint Pattern - Recording Command Pattern - Recording Proxy Pattern - Smart Service Proxy Pattern ---		Context Map-oriented Aggregated Core Services			EDR-aggregated Aggregated Core Services


P1. A service shall have one named owner	P2. A service shall provide documented business value	P20. All services shall be in the service universe	P21. A service shall be categorized (OW SOA category)	P22. A service shall have an "authentication, authorisation, endpoint strategy"
P23. A service shall document its Service Level Agreement SLA (response time, availabillity++)	P3. A service shall do one only thing, and one thing well	P30. A service shall have a versioning strategy (ACS, CS)	P30. A service shall have a versioning strategy (ACS, CS)	P31. A service shall provide for audit and monitoring of service usage
P31. A service shall provide for audit and monitoring of service usage	P32. A service shall document its Service Level Agreement SLA (response time=30ms, availability=99.995%)	P32. A service shall document its Service Level Agreement SLA (response time=30ms, availabillity=99.995%)	P40. A service shall provide at least one Evolving Service Endpoint	P41. A service shall provide heartbeat and traffic monitoring
P90. A service shall have a documented coupling to the contractual and requirement for service usage