Agnostic Capability (324) How can multi-purpose service logic be made effectively consumable and composable?

Agnostic Context (312) How can multi-purpose service logic be positioned as an effective enterprise resource?

Agnostic Sub-Controller (607) How can agnostic, cross-entity composition logic be separated, reused, and governed independently?

Asynchronous Queuing (582) How can a service and its consumers accommodate isolated failures and avoid unnecessarily locking resources?

Atomic Service Transaction (623) How can a transaction with rollback capability be propagated across messaging-based services?

Brokered Authentication (661) How can a service efficiently verify consumer credentials if the consumer and service do not trust each other or if the consumer requires access to multiple services?

Canonical Expression (275) How can service contracts be consistently understood and interpreted?

Canonical Protocol (150) How can services be designed to avoid protcol bridging?

Canonical Resources (237) How can unnecessary infrastructure resource disparity be avoided?

Canonical Schema (158) How can services be designed to avoid data model transformation?

Canonical Schema Bus (709)

Canonical Versioning (286) How can service contracts within the same service inventory be versioned with minimal impact?

Capability Composition (521) How can a service capability solve a problem that requires logic outside of the service boundary?

Capability Recomposition (526) How can the same capability be used to help solve multiple problems?

Compatible Change (465) How can a service contract be modified without impacting consumers?

Compensating Service Transaction (631) How can composition runtime exceptions be consistently accommodated without requiring services to lock resources?

Composition Autonomy (616) How can compositions be implemented to minimize loss of autonomy?

Concurrent Contracts (421) How can a service facilitate multi-consumer coupling requirements and abstraction concerns at the same time?

Contract Centralization (409) How can direct consumer-to-implementation coupling be avoided?

Contract Denormalization (414) How can a service contract facilitate consumer programs with differing data exchange requirements?

Cross-Domain Utility Layer (267) How can redundant utility logic be avoided across domain service inventories?

Data Confidentiality (641) How can data within a message be protected so that it is not disclosed to unintended recipients while in transit?

Data Format Transformation (681) How can services interact with programs that communicate with different data formats?

Data Model Transformation (671) How can services interoperate when using different data models for the same type of data?

Data Origin Authentication (649) How can a service verify that a message originates from a known sender and that the message has not been tampered with in transit?

Decomposed Capability (504) How can a service be designed to minimize the chances of capability logic deconstruction?

Decoupled Contract (401) How can a service express its capabilities independently of its implementation?