UW Information Technology

Service Oriented

Purpose: Promotes re-usability, granularity, modularity, statelessness, loose coupling in solution design. In business terms, this translates into business process flexibility and growth (improved information flow), cost savings, and business advantage opportunities.


  • Deliver business functionality as modular, reusable, loosely-coupled services and messages.
  • Design services and messages to have well-defined interfaces and data models.
  • Design modular components; create building blocks not monoliths.
  • Enable reuse of data and functionality.
  • Make services and messages discoverable.
  • Define boundaries to enable separation of concerns.

Achieving this Guiding Principle

Best Practice
Web service API’s are modeled and designed according to the principles of REST using HTTP 1.1.
Services and their APIs use version strings and document how compatibility is managed between version changes.
Resources exist in at most one web service.
Systems and applications subscribe to events to know when external data has changed.
Systems and applications call Web services to interact with enterprise data.
Systems and applications publish events when external systems need to know when data has changed.
Systems and applications call enterprise Web services for workflow, identity, notification, and document management needs.
Every unique business function is automated by at most one service.
All application functionality is API-enabled.